Why not to release Bitweaver 1.8?

by Kozuch
Monday 07 of May, 2007
Posted to Webmastering Bitweaver
I pretty much like release cycles. I mean fixed release cycles - for example like Ubuntu Linux has. I know that more or less every 6 months new stable release comes out that adds THE features that were coded in the meantime. I do not need tons of new features in every new version of software - I much rather go through constant evolution than experience a revolution once in ten years. What am I little mad about? The development cycle of Bitweaver.

Well, I want to say I really like the ideas behind the Bitweaver project. However, I think that a little bit more "management" would not be bad. For example development management. Can't we really make some reasonable release schedule? Why not to "freeze" once in a while and release the new features as stable? We will get more hits from SourceForce because people see there is development going on and we recieve more feedback and testing from the general public at the same time.

Another thing is some kind of quality assurance - is it OK that new features are being added here and not there, are the docs all right, does the development go the right direction etc. etc. I miss discussion about this. Maybe it is being talked on IRC, but that's not my main channel unfortunatelly. Let's talk in the forums so that anyone can see it and possibly new people can join the project and help out!

Comments

1.5

by Will, 11 May 2007 (19:00 UTC)
would have to be released first.

:)

Re: 1.5

by Kozuch, 12 May 2007 (21:46 UTC)
Sure, I thought 1.8 would be closer to 2.0 though (:evil:)

by spiderr, 15 May 2007 (19:25 UTC)
You can make all the scehdules you want, but without people commited to the process, it is pointless.

R2 is ready. You are welcome to become a release manager, or try to find someone who wants to do it. Make builds, test thoroughly, post files, upload to sourceforge.


Re:

by Kozuch, 17 May 2007 (21:19 UTC)
Spiderr,

I'll always love to help out. I have done some heavier R2 testing about a month ago - cleaned and reviewed our SF bug tracker too. But there is still lots of work left.

I will be happy to be able to manage the releasing a bit. Hope you will not hate me all for that (:rolleyes:).

Re:

by spiderr, 18 May 2007 (00:32 UTC)
Kozuch,

We would love to have your help! The problem of the release has been not enough help. Have you seen ReleaseProcess ? In fact, I will nominate you as ReleaseManager, so when people ask about ReleaseTwo, I will tell them to ask you.

Now, what do you need help with to get the release done?

Re:

by Kozuch, 19 May 2007 (10:49 UTC)
Perfect, I am kind of proud to hear the nomination! (:eek:)

I will stop by on IRC to clear the details!

by WaterDragon, 23 May 2007 (20:11 UTC)
Fixed release cycles almost always take paid developers to make happen. If you would like to hire a team of BitWeaver developers to ensure that releases are made in a timely way I am sure that you could find many willing to accept large bags of cash on #bitweaver. (:wink:)

Getting involved as is mentioned in the comments is the best way to get what you want without the large bags of cash.

Re:

by Kozuch, 25 May 2007 (16:33 UTC)
Thanx for clarifying Nick.