Closed Bug 1357408 Opened 8 years ago Closed 8 years ago

release tracking flag refresh (56)

Categories

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

Production

Tracking

()

RESOLVED FIXED

People

(Reporter: dylan, Assigned: dylan)

References

Details

We don't need 56 flags yet. Nightly is still 55 for another cycle.
Flags: needinfo?(dylan)
(In reply to Ryan VanderMeulen [:RyanVM] from comment #1) > We don't need 56 flags yet. Nightly is still 55 for another cycle. Aha. What about disabling 52?
Flags: needinfo?(dylan) → needinfo?(ryanvm)
Yes, we're still shipping 53 tomorrow :)
Flags: needinfo?(ryanvm)
Does the milestone marker need to be moved up yet?
Flags: needinfo?(cbook)
To clarify, Dylan's asking if: * We are not adding tracking or status flags for FFx 56 because nightly remains at FFx 55 because of the Dawn work. * We still need to disable 52 as a milestone but not add 56 Thanks!
That is my understanding from various threads I've read.
Yes -> * We are not adding tracking or status flags for FFx 56 because nightly remains at FFx 55 because of the Dawn work. so please no status flag update Yes -> * We still need to disable 52 as a milestone but not add 56 hopefully 52 is very soon history :)
Flags: needinfo?(cbook)
This is up to Emma to communicate when we finish adding fields/values for 56. Assign back to me when a decision is ready.
Assignee: dylan → ehumphries
Per :ritu, release management needed the status flags and those were added in bug 1358284. Please disable 52, as a milestone but not add 56. We're going to need to clarify what we mean by milestones vs. tracking flags.
Assignee: ehumphries → dylan
See Also: → 1358284
52 is disabled, and this bug remains up until 56 flags are needed across-the-board, everywhere (e.g. when 55 becomes beta, I believe.)
Finally ready! 12:23 <RyanVM> only 56 12:23 <RyanVM> basically disable 53 tracking flags, unlock 56 ones, make 56 target milestone the default below the ---
I think all of this is done. It's a bit messy because of the project dawn changes, but by the next flag refresh it should be smooth (and maybe a bit more automated)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.