Closed Bug 920868 Opened 6 years ago Closed 6 years ago
Remove shipped milestones from b2g status/tracking flags
As we do with Firefox, we should drop off the oldest version (after it has shipped) so in this case we are more than finished with v1.0 and v1.0.1 so those b2g tracking/blocking and approval flags can be phased out. Still keeping the history on bugs they were set on during development.
So, to be specific: status-b2g18-v1.0.0: status-b2g18-v1.0.1:
Also in the Target Milestone pulldown - we won't be setting milestones for anything v1.0 or v1.0.1
while we are doing this clean-up can we also remove four entries which look like : B2G C1(to nov19) B2G C2(20nov- 10dec) B2G C3(xxxx - xxxxx) B2G C4(xxx)
all done. Committing to: bzr+ssh://email@example.com/bmo/4.2/ modified extensions/BMO/lib/Data.pm Committed revision 9040. i managed to catch bajaj on irc regarding doing this automatically for b2g... <glob> am i correct in saying that the b2g release dates are more "target dates" than hard fixed dates? <glob> the reason why i update the firefox tracking fields/versions/milestones is they have a fixed schedule, so i don't need a bug to remind me to do it <bajaj> ah <glob> if b2g's release dates are fixed, then i can establish a similar process for your fields <glob> if not, you'll have to file a bug when required <bajaj> things are solidyifing still.. <bajaj> so lets give it one more cycle <bajaj> :) <glob> ok :)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Summary: Let's remove shipped milestones from b2g status/tracking flags once they shipp → Remove shipped milestones from b2g status/tracking flags
You need to log in before you can comment on or make changes to this bug.