toylet [mozilla] wrote: > > maybe old news. > > http://www.newsforge.com/article.pl?sid=02/03/04/047229&mode=thread >
I'm still abit sceptical that a march release is too soon.. there are a lot of post 0.9.7, 0.9.8 regressions, nsbeta1+, nsbeta1, and mozilla1.0 nominations as well as bugs targeted at mozilla 1.0.. I've not queried these, but there should be a double milestone, one for the 1.0 targets, nsbeta1+ & regressions that developers know they have time to work on and fix these. I'm going to take the MS way of coding here with a 1.0... 0.9.9 is like an alpha 1.0, where most of the last of large blocks of code/projects are done checking in. 1.0 should be a beta milestone: Release candidate 1... As for the other 2, I mentioned: I'd suggest that be RC2/RTM build. It should cover any of the stuff left for nsbeta1, regressions that are notibly in dire need of fixing, polish and Ui that maybe left if it comes right down to it. People are making good fixes, but I'm finding stuff almost as fast that have regressed in previous nightles, or milestones that come up, :) this kinda follows Brendan's roadmap thinking, where developers shouldn't rely on another milestone after 1.0, but it does follow roadmap thinking after 1.0.. which I think we really need a rock solid build to have RTM. There is only 3 weeks left for a late March early April release. According to the roadmap, 1.0 started almost 2 weeks ago or more, and milestone 0.9.9 is not even out the door here, 1.0 checkins just started a few days ago. -dman84
