Re: 4.0.5: Merge Request

On Tue, Apr 24, 2001 at 11:04:33PM -0700, Rasmus Lerdorf wrote: > Yes, but that is my point. They should not be asking people to fix bugs. > They should simply be identifying and prioritizing the bugs. As a group > we need to fix the bugs. Jani is complaining that they are ignored, so we > need to change the atmosphere and remove that aspect from their duties. > We are not going to change the way developers do their day-to-day jobs by > much. But by changing the approach to one that is centered around an > itemized list of issues I think we will completely change how things work. > Imagine if there is only 1 criticl bug left on the list and it is in a > piece of code you wrote? Everyone sees this list and everyone can see > that as soon as this bug is fixed the release can go out. That will > motivate a developer into holding off on playing with cool new features > and taking a look at the bug. > > The question right now is how to best implement this. Do we add something > to the bug database to flag bugs in some manner and have a release > candidate summary page? > > Or do we separate it out of the bug database and maintain the list > manually? I don't have any personal experience with the Mozilla "solution" to this issue, but I'm sure someone else where must know more about it than me. Anyway, they appear to have some sort of "voting" system in place, tied into Bugzilla. Each user or developer votes on which bugs s/he thinks should be closed before the next milestone is released. If a bug receives enough votes, it becomes a required bug fix. Adopting a system like this would mean hacking on our current bug system, and I don't have time or code to back that up right now (although I really wish I could). Perhaps someone else will be able to step in there, though. -- Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member