As you might have noticed, progress isn't going as fast as we all would like to see. But we feel that it's time to get our first 2.0 alpha version out soon because many people have already switched to the SVN version.

This first 2.0 release won't differ much from the 1.0 version functionality-wise, but under the covers things have changed quite a bit to have a solid foundation for the upcoming stuff.

We'll put in everything we have so far and also include some contributions that have been made by various users. Notice that it will be an alpha version, so there might be some small API changes in the next versions.

After releasing 2.0 alpha, the module development guide will be updated, because there are some important changes that benefit module developers.

A mailing list to discuss developer topics is created at Sourceforge. Visit http://lists.sourceforge.net/lists/listinfo/cuyahoga-devel to subscribe.

The fact that you can read this means that the site was successfully migrated :).

This site is going to move to a new web host today. We suffered from some performance issues lately that were out of our control unfortunately.
John Paul Mains of Softwyre graciously offered the new hosting space. Thanks a lot for that!

During the migration, the forum won't be available to make sure nothing gets lost.

After weighing all pro's and cons, we think it's time to move development to .NET 2.0 framework. The driving forces behind this move are:

• (obvious) A more powerful development environment
• The web application project model is released
• Standards compliance. In .NET 1.1 it's nearly impossible to build valid XHTML sites and with 2.0, this is much easier
• Innovation. One of the benefits of working on an OS project is the learning experience. Staying on .NET 1.1 makes the project a lot less interesting for many people in this area.

Against a whole lot of pro's there is one very big con: Mono support. The .NET 1.1 support is pretty complete in Mono, but the 2.0 support is not. This means that it might be possible that the next generation of Cuyahoga (2.0) will not work on Mono when it's released. We'll keep a separate branch of the 1.x version that will continue to work on Mono, but all new development will be in the 2.0 version.
It was a very hard decision to make. Mono support is one of the key features of Cuyahoga (in fact, it was the main reason why Cuyahoga was started) and we still like to keep supporting Mono, but at this moment, we want to move forward.