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.
#13 Re: Re: Re: awesome....
Wednesday September 4th, 2002 11:53 PM
You are replying to this message
I guess I'll let you tell Jag and Darin that the 10% pageload performance gain they made (more gain than was made in the previous 10 months combined) wasn't meaningful. I'll let you explain to Aaron that his type ahead find isn't a meaningful improvement. And while you're at it why don't you tell the bi-di developers that the dozen or so fixes they've landed including making text selection finally work isn't meaningful. Oh, and tell sspitzer that his fix for the most frequently reported mailnews bug ever wasn't meaningful work. And don't forget to tell darin that prefetching LINK tag documents isn't a meaningful change either. And while you're on a roll tell alecf that we didn't really need to handle visited links properly and tell brade that we didn't need that horrible text area scrolls on space bug fixed and tell all the mailnews team that the 100+ bugs they fixed weren't meaningful and tell all the browser and composer developers that the 800+ bugs they fixed weren't meaningful either. And what reasonable person would ever consider 68 hang, crash and topcrash fixes meaningful? 6 dataloss fixes? Definitely meaningless. Over 30 performance improvements? Completely meaningless. Another 20 standards support bugs fixed? Completely without meaning.
OK, I know you said "too short to allow for _much_ meaningful work to occur." You're probably not alone in thinking that. But just because some of the Mozilla developers were paying more attention to the 1.0 branch doesn't mean that the trunk stood still. 1.2alpha will have been under heavy development for roughly 5 weeks taking about 1000 fixes. It's time to slow things down for a few days, get something in the hands of our Milestone testers, get some talkback data and start cleaning things up for 1.2beta. But don't fret if you've still got a lot of bugs to fix for this release. We've got 8-10 weeks of development in the cycle before we release Mozilla 1.2final and that should be enough time to get our most important 1.2 issues solved.