Closed Bug 1554851 Opened 5 months ago Closed 5 months ago

Let ARM64 Fennec 68 ride the trains from Beta to Release

Categories

(Release Engineering :: Release Automation: Pushapk, task)

ARM64
Android
task
Not set

Tracking

(firefox67 wontfix, firefox67.0.1 wontfix, firefox68blocking fixed, firefox69 fixed)

RESOLVED FIXED
Tracking Status
firefox67 --- wontfix
firefox67.0.1 --- wontfix
firefox68 blocking fixed
firefox69 --- fixed

People

(Reporter: cpeterson, Assigned: jlorenzo)

References

Details

(Whiteboard: [bcs:p1])

Attachments

(4 files)

Johan, I have a calendar reminder to file this bug asking you to remove the hold preventing ARM64 Fennec 68 from riding from Beta to Release. We must ship ARM64 in 68 to meet Google's August 1 deadline requiring 64-bit apps. Fortunately, ARM64 Fennec 68 Beta is looking good and there are no release blockers.

This is follow-up work from "Let ARM64 Fennec 67 ride the trains to Beta" bug 1520261.

Flags: needinfo?(jlorenzo)

Hey Chris! Thanks for confirming the publication! I'll make sure ARM64 ships with the rest of Fennec Release.

Flags: needinfo?(jlorenzo)
Pushed by jlorenzo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2ff50159f61f
Let ARM64 Fennec 68 reach the release population r=mhentges
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED

Please nominate this for Beta approval when you get a chance.

Flags: needinfo?(jlorenzo)

I wish I could use the approval flag, but it's not set for this bugzilla component. I'll follow up with Releng to know if we want to activate it.

Beta/Release Uplift Approval Request

  • User impact if declined: Fennec 68 Aarch64 won't be shipped
  • Is this code covered by automated tests?: Yes, whenever a release is kicked off.
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: No
    If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): The effect of the code is immediately visible when a release is kicked off: either aarch64 is scheduled to be shipped or it's not. I'll make sure it is, thanks to the Fennec ESR plan. There is no impact for the end user.
Flags: needinfo?(jlorenzo) → needinfo?(jcristau)

a=jcristau for the patch in comment 7 on mozilla-beta.

Flags: needinfo?(jcristau)
Whiteboard: [bcs:p1] → [bcs:p1][checkin-needed-beta]

$ hg graft -e -r 2ff50159f61f
grafting 532557:2ff50159f61f "Bug 1554851 - Let ARM64 Fennec 68 reach the release population r=mhentges"
merging taskcluster/taskgraph/loader/push_apk.py
merging taskcluster/taskgraph/transforms/push_apk.py
warning: conflicts while merging taskcluster/taskgraph/loader/push_apk.py! (edit, then use 'hg resolve --mark')
warning: conflicts while merging taskcluster/taskgraph/transforms/push_apk.py! (edit, then use 'hg resolve --mark')
abort: unresolved conflicts, can't continue
(use 'hg resolve' and 'hg graft --continue')

Flags: needinfo?(jlorenzo)
Whiteboard: [bcs:p1][checkin-needed-beta] → [bcs:p1]

(In reply to Julien Cristau [:jcristau] from comment #11)

$ hg graft -e -r 2ff50159f61f
grafting 532557:2ff50159f61f "Bug 1554851 - Let ARM64 Fennec 68 reach the release population r=mhentges"
merging taskcluster/taskgraph/loader/push_apk.py
merging taskcluster/taskgraph/transforms/push_apk.py
warning: conflicts while merging taskcluster/taskgraph/loader/push_apk.py! (edit, then use 'hg resolve --mark')
warning: conflicts while merging taskcluster/taskgraph/transforms/push_apk.py! (edit, then use 'hg resolve --mark')
abort: unresolved conflicts, can't continue
(use 'hg resolve' and 'hg graft --continue')

Sorry, I landed the patch before notificing your NI. The rebased patch is attachment 9069341 [details]. It's the one I landed in comment 12.

Flags: needinfo?(jlorenzo)
See Also: → 1568674
You need to log in before you can comment on or make changes to this bug.