Trunk Freezes for 1.2 Alpha Tonight
Tuesday September 3rd, 2002
The main development trunk will be frozen at 11:59pm tonight Pacific Daylight Time and will remain frozen until 1.2 Alpha is released. While the freeze is in effect, all checkins to the trunk will require approval from firstname.lastname@example.org. Like 1.1 Alpha and 1.1 Beta, 1.2 Alpha will probably be released directly off the trunk with no branching beforehand. The ideal release date is Friday 6th September, though this may change. See the Roadmap for more details about release plans and tinderbox for the current status of the trunk.
#19 Release Cycle & Feature plan
by gadeiros <Harald@Henkel.DAH.UUnet.DE>
Friday September 6th, 2002 2:25 AM
You are replying to this message
First of all, I want to make clear, that I appreciate greatly, what you and all the other Mozilla developers do. It's simply great work. And I don't intend to burden you with additional workload or keep anyone from what he does/likes best: coding.
I guess, that there has been a lot of discussion on the planned release cycle with new x.y versions every 3 month. I just intend to suggest a slightly different one, like that of e.g. KDE: about 6 month for x.y with additional features and about 6 weeks for x.y.z with only bug and security fixes (mainly backported from the x.y+1 development).
About "Users can see what changed _after_ the release. Developers and testers can see what's going to change _before_ the release."
I know, all the information is available ... somehow.
Open source development has a lot of aspects. One is, that there are a lot of people intersted in its ongoing progress. Not only some developers and a realatively small bunch of testers.
End of July lwn.net announced that they would have to stop their activity, because they have too much work with that "project" and don't get paid for it. They received immediately hundreds of messages with suggestions how to go on and about >10000$ of donations in a couple of days, because a lot of people love that service. One of the pages there with the most hits seems to be the Kernel Development page and the people reading it are not the kernel hackers or testers, but people who are just interested in reading what's going on. The same is true with the Kernel Cousins for various projects (KDE, Wine, etc.).
These are all done not by the developers themselves but people who are just interested in that development and have enough time and interest to do it - and it takes a lot.
This is strangely missing for Mozilla (or I have been too blind/stupid to find it).
About the "What's New".
Do you create this section, starting short before the release , extracting all the relevant information from the change logs and other sources ? Or do you do this on a daily or weekly basis (which I would find more convenient). Then why not publish the results updated daily/weekly ?
On the other hand, I still don't understand, if there is some plan, which features should go into the next release, and this is just hidden behind some Bugzilla bugnumber, or if the developers just code what comes into their mind and the "What's New" is really compiled from change logs.
Of course the feature plan of my pet example KDE is created similarly, be developers stating what came into their mind they liked to do/code and somebody compiling a list of this. Then the status is roughly followed (planned=red,mostly done=yellow,finished=green). And sometime the featureplan is closed for additions - and a feature plan for the following release is opened.
This all is easly accessible through <http://www.kde.org> and doesn't have to be searched in a "bug" database.
From my point of view, it would be really nice, if Mozilla would have something like that, i.e. some kind soul/s with enough time and interesst could be found doing it (i.e. would step up to do it ;-) ).
With kind regards, Harald Henkel