On Fri, 28 Jan 2005, bulia byak wrote:
On Fri, 28 Jan 2005 17:44:29 -0800 (PST), Bryce Harrington <bryce@...260...> wrote:
Please give a more detailed case for why this should be accepted as a release-stopper bug. This has been in the tracker for a while but this is the first time it has been identified as a potential showstopper.
- It's recent. 2) I listed it as critical in my "critical bugs"
message. 3) It was reported by two people already one of which is Jimmac (he's on a Powerbook). 4) If it crashes on PPC this means something is very broken in the code, even if it happens not to crash on i86.
It absolutely must be fixed.
Okay, thanks, that is a good case for this being a must fix.
I think before we accept it, though, we also need a commitment from someone to own the bug. I am worried if we have unowned must-fix bugs, then the release schedule will get messed up.
I'll go over your critical bug list and identify ones that look acceptable as showstoppers and which need more.
Next release, I think we need to be more stringent about getting the must-fix list identified earlier on in the release cycle, so that there is more time to work on them. The only reason I felt comfortable setting dates was because I had asked for must fix bugs, and none were identified (in fact, iirc you had said you were comfortable going ahead with the release)...
Bryce