Closed Bug 1493028 Opened Last year Closed Last year

ESR60 release graphs should have higher priority than low

Categories

(Release Engineering :: Release Automation: Signing, enhancement)

enhancement
Not set

Tracking

(firefox-esr60 fixed, firefox62 unaffected, firefox63 unaffected, firefox64 fixed)

RESOLVED FIXED
Tracking Status
firefox-esr60 --- fixed
firefox62 --- unaffected
firefox63 --- unaffected
firefox64 --- fixed

People

(Reporter: nthomas, Assigned: nthomas)

References

Details

Attachments

(1 file)

It looks like we have these priorities for signing
 mozilla-release:    highest
 mozilla-beta:       high
 mozilla-central:    medium
 mozilla-esr60:      low

So the 60.2.1esr release is currently waiting for firefox and deved 63.0b8 to process first.

The options [1] are 
    highest
    very-high
    high
    medium
    low
    very-low
    lowest
    normal

Aki suggested making esr60 high to match beta. Any thoughts Ryan ?

[1] https://docs.taskcluster.net/docs/reference/platform/taskcluster-queue/docs/task-schema
very-high makes sense to me
Blocks: esr60
Comment on attachment 9010818 [details]
Bug 1493028 - update branch priorities for esr60, r?aki

Aki Sasaki [:aki] has approved the revision.
Attachment #9010818 - Flags: review+
Pushed by nthomas@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5644bce7acbb
update branch priorities for esr60, r=aki
https://hg.mozilla.org/mozilla-central/rev/5644bce7acbb
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.