0.9.2 Branch and Beyond
Sunday June 24th, 2001
Chris Blizzard has posted an update on current tree management plans for the 0.9.2 branch and the 0.9.3 trunk. The plan calls for mozilla.org to drop the requirement of firstname.lastname@example.org approval for check ins to the trunk, while continuing it till 0.9.2 is finished on the branch. Chris felt that using 0.9.2 as a stability milestone was a success, partly thanks to the drivers requirement, but mostly due to better self policing by those who were checking in.
#35 Re: The point is the goals changed!!
Tuesday June 26th, 2001 3:14 PM
You are replying to this message
I'm not sure why you continue to resort to ad hominem. Just so you'll know, my first training in software engineering was directly from Dr. Brooks, about twenty years ago. I am a software manager, I have often acted as a project manager, and I have managed project managers, as well as working in close conjunction with QA leads and managers for many years. I'm tempted to quiz on you on some basic software process issues, but I'm trying to avoid desending to the personal level that has dominated this discussion so far.
I don't see the relevance of your observation. Stability milestones are for bug fixing. You can't allow in high-risk fixes during a stability milestone, but you also don't cut it so short that you can't reach your bug fixing goals. In fact, you're not even saying that those bugs were locked out because they were high risk (which would make sense) -- you're saying they were just dropped due to a changed deadline. Saying that it was fine to ship with scaled back bug-fixing goals because it was a stability milestone is very nearly an oxymoron.