need more milestones: mozilla1.3a/b, mozilla1.4a/b, mozilla1.5a/b

VERIFIED FIXED

Status

()

bugzilla.mozilla.org
Administration
VERIFIED FIXED
16 years ago
7 years ago

People

(Reporter: Biesinger, Assigned: asa)

Tracking

Details

The Browser component should have more milestones, at least 1.1 and 1.2 would be
nice, but even some after that would be no bad idea.

People have already started using ancient milestones for bug categorization due
to lack of more than 3 future milestones, which makes them useless for the
purpose of finding out when a bug is likely to be fixed.

Comment 1

16 years ago
mozillaV<release> is driven by keywords so there's no need for those target
milestones, but we do need a few more future points so people don't decide to
abuse the older milestones.
Summary: need more milestones → need more milestones: mozilla1.3a/b, mozilla1.4a/b, mozilla1.5a/b
releases are not driven by keywords, they're driven by drivers and developers
sending drivers requests for approval. how would you mark a bug that you'd want
to fix for 1.2 RTM?

Comment 3

16 years ago
i'd attach a patch, set the milestone to 1.3a, add mozilla1.2 to the keyword
list, and email drivers.
hm.... if you insist on that...
having the milestones mentioned in the summary would already be a great step ahead
(Assignee)

Comment 5

16 years ago
We now have milestones till January. If you're planning past january with a 5
week granularity then I suspect you're ahead of the pack. 
(Assignee)

Comment 6

16 years ago
.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED

Comment 7

16 years ago
vrfy fixed for Browser and MailNews

The following appear to be using the same general versioning schema but have not
been given the extra milestones.
CCK
Directory
Mozilla Localizations
mozilla.org 
Status: RESOLVED → VERIFIED
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.