New Release, New Release Schedule, New Release Approach

Anonymous • 23 Jan 2009 (17:52 UTC)



by , 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 , 15 Feb 2009 (07:18 UTC)
we thank you! great entry on demolab.com.


by , 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 , 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.
  Page 1 of 1  1