Closed
Bug 1197088
Opened 9 years ago
Closed 9 years ago
Add tracking-firefox-esr38 41+ option
Categories
(bugzilla.mozilla.org :: Administration, task)
Tracking
()
RESOLVED
FIXED
People
(Reporter: dveditz, Unassigned)
References
Details
Please add a '41+' option to the tracking-firefox-esr38 flag. lmandel: do we really want to add these one at a time? We could just add 41+ through 46+ now and not have to worry about it again for the life of ESR38
Flags: needinfo?(lmandel)
Comment 1•9 years ago
|
||
(In reply to Daniel Veditz [:dveditz] from comment #0) > Please add a '41+' option to the tracking-firefox-esr38 flag. > > lmandel: do we really want to add these one at a time? We could just add 41+ > through 46+ now and not have to worry about it again for the life of ESR38 41+ added. Close this unless there are nomore to be added.
Comment 2•9 years ago
|
||
Sylvestre - Can you please make a call on whether to add all the flags now as suggested in comment 0.
Flags: needinfo?(lmandel) → needinfo?(sledru)
Comment 3•9 years ago
|
||
Daniel, currently, will you use an higher number than 43 (nightly now)? If not, we can just ask the bmo admin to update their post-merge todo list to manage that for us? (I think I remember glob telling me that they are doing a bunch of things during the merge day). Instead of having values which won't be used for the next few months
Flags: needinfo?(sledru) → needinfo?(dveditz)
Reporter | ||
Comment 4•9 years ago
|
||
It would be nice to have releases available that are higher than the current one--there are several bugs that I'd like to slot for 42+ but are too late/risky to push to beta right now--but yes, "current nightly" is the highest I would ever expect to need.
Flags: needinfo?(dveditz)
(In reply to Daniel Veditz [:dveditz] from comment #4) > yes, "current nightly" is the highest I would ever expect to need. added 42+ and 43+, updated process to add when we add new milestones.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•