1493028 - ESR60 release graphs should have higher priority than low

Status: RESOLVED FIXED

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

Description

[Nick Thomas [:nthomas] (UTC+12)]

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

[Ryan VanderMeulen [:RyanVM]]

very-high makes sense to me

Comment 2

[Aki Sasaki (not active)]

very-high would match esr52 in https://hg.mozilla.org/mozilla-central/file/default/taskcluster/taskgraph/transforms/task.py#l692 .

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

Attachment: Bug 1493028 - update branch priorities for esr60, r?aki

Comment 4

[Aki Sasaki (not active)]

Comment on attachment 9010818 [details]
Bug 1493028 - update branch priorities for esr60, r?aki

Aki Sasaki [:aki] has approved the revision.

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/5644bce7acbb
update branch priorities for esr60, r=aki

Comment 6

[Nick Thomas [:nthomas] (UTC+12)]

https://hg.mozilla.org/releases/mozilla-esr60/rev/078cec67c7046b31d141c408958e8ebe7521f7e2

Comment 7

[Eliza Balazs [:ebalazs_]]

https://hg.mozilla.org/mozilla-central/rev/5644bce7acbb