Closed Bug 1531858 Opened 6 years ago Closed 5 years ago

Update Focus 8.0 to a newer GV 68 Nightly version

Categories

(GeckoView :: General, task, P1)

All
Android

Tracking

(firefox66 wontfix, firefox67 wontfix, firefox68 affected)

RESOLVED FIXED
Tracking Status
firefox66 --- wontfix
firefox67 --- wontfix
firefox68 --- affected

People

(Reporter: cpeterson, Assigned: droeh)

References

Details

(Whiteboard: [geckoview:fenix:m7])

GV 67 Nightly will ride to Beta on March 18. We should update Focus (Nightly and 8.0 release) to GV 67 Beta to get more user testing. GV 67 is the version that will ship in Fenix.

New GV Beta builds are produced once a week. We'll probably want to update Focus's GV 67 Beta snapshot weekly.

Blocks: 1531862

Focus's reminder to update to GV 67 Beta:
https://github.com/mozilla-mobile/focus-android/issues/4222

Assignee: nobody → droeh
Blocks: 1530757
No longer depends on: 1530757

Deferring to [geckoview:fenix:m4] because Dylan is going on PTO for two weeks and Vesta says updating Focus can wait until April.

Whiteboard: [geckoview:fenix:m3] → [geckoview:fenix:m4]
Summary: Update Focus to GV 67 Beta → Update Focus to GV 68 Nightly

I've got a PR up that updates Focus to GV 68 and AC 0.49.0; https://github.com/mozilla-mobile/focus-android/pull/4243

Focus 8.0.9 with GV 68 is now live in the Google Play Store. Dylan says he will update Focus 8.0 to a more recent GV 68 version (with the fix for Android Q crash bug 1543555) after AC 0.51.0 is released.

https://github.com/mozilla-mobile/android-components/releases

Type: enhancement → task
Depends on: 1543555
Summary: Update Focus to GV 68 Nightly → Update Focus 8.0 to a newer GV 68 Nightly version
Whiteboard: [geckoview:fenix:m4] → [geckoview:fenix:m5]

Adding [geckoview:fenix:m7] whiteboard tag because this bug is important but not strictly a Fenix MVP release blocker.

Whiteboard: [geckoview:fenix:m5] → [geckoview:fenix:m7]

Dylan already fixed this.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.