Closed Bug 1488402 Opened 6 years ago Closed 6 years ago

Tracking flags refresh (64)

Categories

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

Production
task
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: pascalc, Unassigned)

References

Details

Today is merge day. Nightly is moving from 63 to 64. We need BMO flags to be updated to support this new version (Version, Target Milestone, Firefox tracking flags including relnotes). Thanks
Flags: needinfo?(dylan)
Also support for esr52 is ending so we can disable the related status/tracking flags.
:dylan is traveling today. :dkl, please work on milestones and versions, including those for DevTools, WebExtensions, and the GeckoView product. I'll work on status and tracking flags, including disabling esr52.
Flags: needinfo?(dylan)
* esr52 flags disabled * Firefox 61 flags disabled * Added 64+ to and removed 61+ from esr60 tracking flag * Added 64+ to and removed 61+ from relnote tracking flag
Should we use "Branch NN" or "NN" for version in Thunderbird?
Flags: needinfo?(vseerror)
Flags: needinfo?(jorgk)
Versions and milestones done except for Thunderbird.
Flags: needinfo?(dkl)
You can do whatever we had before. Mailnews had NN, TB had "NN Branch" to NN=58 and raw NN after that. So let's go with NN. Thanks for taking care of it!!
Flags: needinfo?(vseerror)
Flags: needinfo?(jorgk)
(In reply to Jorg K (GMT+2) from comment #7) > You can do whatever we had before. Mailnews had NN, TB had "NN Branch" to > NN=58 and raw NN after that. So let's go with NN. Thanks for taking care of > it!! Then versions is done as well.
We still need tracking flags: tracking-thunderbird64, status-thunderbird64. Thanks in advance.
:jorg, will you continue to support esr52 or should I disabled the associated flags?
We're not supporting it any more, but I guess the access should stay just the same, maybe to correct flags. I think we can do the clean-up a little later. Thanks for asking.
Flags: needinfo?(jorgk)
(In reply to Jorg K (GMT+2) from comment #11) > We're not supporting it any more, but I guess the access should stay just > the same, maybe to correct flags. I think we can do the clean-up a little > later. Thanks for asking. I've removed them from being set on new bugs, but they are still active. Here's the list of bugs with one or both of those tracking flags set if someone from your team would like to go through them: https://mzl.la/2wIpZT5
At least the Devtools product also needs the 64 milestone added.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.