Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | REMIND and LATER considered harmful | ||
---|---|---|---|
Product: | Infrastructure | Reporter: | Unknown <non-migrated> |
Component: | Bugzilla | Assignee: | michael.bemmer |
Status: | CLOSED WONT_FIX | QA Contact: | issues@ooo <issues> |
Severity: | Trivial | ||
Priority: | P4 | CC: | issues, mdekkers, rbircher, stx123 |
Version: | current | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Other OS | ||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Unknown
2002-04-30 20:19:37 UTC
This makes sense. Louis? Hi, this does make sense but it is really Michael Bemmer's call, as he is the main organizer of IssueZilla. It is possible that these characterizations are used by some projects more than others. But, for my money, I think that if we are to suggest modifications on the IZ template, then we should include this one. adding stefan to cc list. and changing to enhancement, not defect. Reassigning to Michael. Lowering priority. louis Maybe somebody can enlighten me: what is all this discussion about Bugzilla and "Netscape employees" about? We're dealing with OpenOffice.org and IssueZilla here. Regarding the enhancement itself: yes, I agree, calling something that's just postponed "resolved" is not really correct. I'd vote for removing the stati "later" and "remind", too, and work with milestones instead. So I accept this issue, but see no high priority to get this implemented. The mozilla/netscape discussion is cut and pasted discussion from bugzilla.mozilla.org; sorry if that was confusing. The issues that they face in their bugzilla are in many ways identical to the ones OOo face here, so I thought it might be of some use to see how they've dealt with it (given that they've now got several years of bugzilla experience and roughly 20 times as many filed bugs as you guys do.) [Whether or not 20 times more bugs is a sign of success or failure is debatable, I suppose ;) but they haven't gone insane yet... ;) Reset QA Contact to new default Old CEE Issue, so I will close it. |