920868 - Remove shipped milestones from b2g status/tracking flags

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Administration, task, major)

Description

[Lukas Blakk [:lsblakk] use ?needinfo]

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.

Comment 1

[Lukas Blakk [:lsblakk] use ?needinfo]

So, to be specific: 

status-b2g18-v1.0.0: 	
status-b2g18-v1.0.1:

Comment 2

[Lukas Blakk [:lsblakk] use ?needinfo]

Also in the Target Milestone pulldown - we won't be setting milestones for anything v1.0 or v1.0.1

Comment 3

[bhavana bajaj [:bajaj]]

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)

Comment 4

[Byron Jones ‹:glob› 🎈]

all done.

Committing to: bzr+ssh://[e-mail]/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 :)