Mozilla 0.6 released

Wednesday December 6th, 2000 today released a milestone based on the Netscape 6 branch. Builds are available on the ftp site, and more info on the build and it's purpose is available in the release notes.

#44 Trunk release soon

by asa <>

Saturday December 9th, 2000 12:53 PM

You are replying to this message

I will be working to make a release happen in the next couple of weeks. I'm still not 100% sure what it's going to be called. It'll either be called Mozilla 0.7 or Mozilla 0.8.

My original thinking was that it would be called 0.8 to diferentiate it from the 0.6 branch build (which, btw, was called Mozilla 0.6 because we thought that would help people tie it to Netscape 6.0 and the MN6 branch).

My intent for the next release (0.7 or 0.8) was to get something in the release directory as quickly as possible so that folks who only download Milestones would have something more relevant than this old branch 0.6 build. To this end it is my intent to just pick a good trunk build, update the start page and the little bit of UI change we do for milestones and drop it into the release directory.

This means that developers and QA can't really target work for this release. However, since I created the mozilla0.8 target milestone and keyword in bugzilla a number of developers have started targetting work against them. I think it would be kind of rude for me to pull the rug out from under that triage and tell them that I'm using 0.8 for a build that may or may not include thier work. So now I'm considering just calling the next trunk release Mozilla 0.7. Does this make sense.

Mozilla 0.7 would happen like this. In a couple of weeks (sometime around Christmas) I would look back across all the December daily builds, and pick the best one. Then leaf and I would tag that point on the trunk and make release builds from there.

Mozilla 0.8 would hapen like this: Developers would continue to target and work on bugs for this Milestone. About 5 or 6 weeks after Mozilla 0.7 we would tighten down on the tree and have a few days of stabilization and make a Milestone there (traditional milestone making process).

We will be doing some work on the roadmap.html and Milestone docs to reflect this thinking. What do you all think?