68 train: Rename `{promote,ship}_fennec` into `{promote,ship}_fennec_beta`
Categories
(Release Engineering :: Release Automation: Other, task)
Tracking
(firefox68 fixed)
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: jlorenzo, Assigned: jlorenzo)
References
Details
Attachments
(3 files, 1 obsolete file)
We will need to spin {promote,ship}_fennec_release
off mozilla-esr68. Therefore, let's rename the existing target tasks now and introduce the new ones later.
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
Comment 3•5 years ago
|
||
Could you update the braindump params files to match?
Assignee | ||
Comment 4•5 years ago
|
||
Thanks for spotting that, Aki. I ended up creating new param files, instead of changing the existing ones. The reason is: this current patch is intended to land on mozilla-beta only. So I kept the params as is, until we decide to kill Fennec on mozilla-central for good. (We haven't retired it from there, just in case we want to revert the whole "Fennec ESR" plan at the last minute)
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
I'm worried that some files will always break if I run them against mozilla-central, or some other against mozilla-beta. Is there a way to filter out which files (under the same folder) are 68-compatible and some should be run against 69 or 67?
Comment 7•5 years ago
|
||
(In reply to Johan Lorenzo [:jlorenzo] from comment #4)
Created attachment 9069925 [details] [diff] [review]
[build/braindump] taskgraph-diff: Create params files for the 68 train (Fennec sunset)Thanks for spotting that, Aki. I ended up creating new param files, instead of changing the existing ones. The reason is: this current patch is intended to land on mozilla-beta only. So I kept the params as is, until we decide to kill Fennec on mozilla-central for good. (We haven't retired it from there, just in case we want to revert the whole "Fennec ESR" plan at the last minute)
Aha. Then, if the params files are useful for you or for the rest of the team, we can put them in a separate params dir, possibly params-fennec/
or params-fennec-68
. (If not useful, let's not :) I'd like to allow for testing against 68 code if it's useful, while still allowing someone running on central to run the full set of parameters in params/
.
Assignee | ||
Comment 8•5 years ago
|
||
I agree we don't need the desktop params, just the Fennec ones. I put just the fennec-related files under params-fennec-68
, like you suggested. Thanks!
Comment 9•5 years ago
|
||
Comment 10•5 years ago
|
||
Assignee | ||
Comment 11•5 years ago
|
||
bugherder uplift |
Assignee | ||
Comment 12•5 years ago
|
||
Assignee | ||
Comment 13•5 years ago
|
||
All patches landed/deployed. Closing this bug as fixed.
Please reply in this bug, if you'd like an alternative approach on the braindump patch, I'll be happy to reply back/address it.
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Description
•