Closed
Bug 99207
Opened 22 years ago
Closed 18 years ago
[meta] Meta bug for meta bug changes :-)
Categories
(Bugzilla :: Bugzilla-General, enhancement)
Tracking
()
RESOLVED
INVALID
People
(Reporter: gagan, Assigned: myk)
References
Details
(Keywords: meta)
Updated•22 years ago
|
Severity: normal → enhancement
OS: Windows 2000 → All
Hardware: PC → All
Target Milestone: --- → Future
Comment 1•22 years ago
|
||
This relies on Future stuff so is Future. If Myk wants to commit to doing this and up the milestone, he can do so, and change the status to ASSIGNED.
Keywords: meta
Target Milestone: --- → Future
Assignee | ||
Comment 2•22 years ago
|
||
Re-targeting to Bugzilla 2.18 milestone, since I plan to work on these bugs during that timeframe if not sooner. Leaving the NEW status since I do not change bugs to ASSIGNED until I start working on them (so other Bugzilla hackers know which bugs I am actively working on and which ones could be taken over by someone sufficiently motivated to tackle the problem).
Target Milestone: Future → Bugzilla 2.18
Comment 3•19 years ago
|
||
Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Comment 4•19 years ago
|
||
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
![]() |
||
Comment 5•18 years ago
|
||
closing this meta-bug due to a severe lack of activity.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
Target Milestone: Bugzilla 2.22 → ---
Updated•10 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•