[5]

New Release, New Release Schedule, New Release Approach

spiderr • 23 Jan 2009 (17:52 UTC)
Announcements
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.

Comments

Releasing

by Kozuch, 02 Feb 2009 (11:11 UTC)
I think jump from non-scheduled releases to releasing each 2 months is way too much. Stable half-year releasing would be enough in this case.

Bitweaver demos updated at demolabo.com

by webmaster denolabo.com, 09 Feb 2009 (13:21 UTC)
Hi there,
I let you know that Bitweaver demos have been added to our website : demos are now available in Englsih, Frecn, Spanish, German, Portuguese, Arabic. See demolabo.com/bitweaver

Help us spread the word -)
Thanks in advance.

Re: Bitweaver demos updated at demolabo.com

by xing, 15 Feb 2009 (07:18 UTC)
we thank you! great entry on demolab.com.

x

by Bobby Richardson, 12 Mar 2009 (08:44 UTC)
At first I didn't think 6x/year was that great an idea; but on reflection I think it is, because it'll give site ops a shorter window in which to look for bug fixes, code optimizations, etc.; rather than some unspecified time 'in the future.'

And yeah. 'Decoupled growth of packages.' Nice turn of phrase, that.

Re: Release Schedule and Seasonal themeing

by spiderr, 25 Mar 2009 (03:30 UTC)
FYI, we've whiddled it down to 4 times per year, once per season. It would be nice if someone could doctor up the heading to reflect the current season (and therefore release). Like put some fresh green grass on the header bar with "bitweaver 2.6" nestled in it. And how about some animated grasshoppers. Oh, and butterflies just like Microsoft. We need LOTS of butterflies. Ok, I'll stop now. Seriously, would nice to have a visual connection between current season and current release.

In fact it would be great to have 4 themes based on the 4 seasons.