New Release, New Release Schedule, New Release Approach

We have created bitweaver2.5 in the builds directory. This will go into sf.net release later today, unless I hear someone scream.

Please test now. Either download a copy for yourself, or register at http://testing.bitweaver.org and push all the bells and whistles you can. That site will be nuked shortly.

We need help running administrivia for the release. Please volunteer.

Along with this new release, we have changed our approach to releasing. For 5 years now (fear), we have been very conservative releasing rock solid releases that have locked schemas intermittently. That has bound us up, and greatly stunted our growth. 2.5 allows for proper version checking of package dependencies, and forces an installer run if things don't match. Kudos to /xing for getting this in, and should be a boon for allowing decoupled growth of packages.

We now plan on releasing 6 times a year, regardless the state where we are and where think we might be. See the Bitweaver Release Schedule.

We are no longer running cvs branches (in fact we haven't for several years now) because the merging is WAY too painful. Some packages need branch/merge, and those are handled ccordingly.

Lastly, DO NOT CHECK IN BROKEN CODE. This has been the unstated rule for years now as well, now it is stated.