Closed
Bug 1493028
Opened 6 years ago
Closed 6 years ago
ESR60 release graphs should have higher priority than low
Categories
(Release Engineering :: Release Automation: Signing, enhancement)
Release Engineering
Release Automation: Signing
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
|
||
Comment 1•6 years ago
|
||
very-high makes sense to me
|
||
Comment 2•6 years ago
|
||
very-high would match esr52 in https://hg.mozilla.org/mozilla-central/file/default/taskcluster/taskgraph/transforms/task.py#l692 .
|
Assignee | |
Comment 3•6 years ago
|
||
|
|
||
Comment 4•6 years ago
|
||
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
|
|
Assignee | |
Comment 6•6 years ago
|
||
| uplift | ||
Assignee: nobody → nthomas
status-firefox62:
--- → unaffected
status-firefox63:
--- → unaffected
status-firefox-esr60:
--- → fixed
|
||
Comment 7•6 years ago
|
||
| bugherder | ||
You need to log in
before you can comment on or make changes to this bug.
Description
•