1648894 - Firefox Beta 79.0.0 Release

Status: RESOLVED FIXED

(Release Engineering :: Release Requests, task)

Description

[Chenxia Liu [:liuche]]

Filing this bug for the 79.0.0 release a little early (so as to have a smooth transition from the Firefox Beta 78 release).

This build will include the Performance Experiment (involving the two GV 79 builds with different compile-time flags), and will also be our RC for Firefox Production.

(The early QA build for this is 78.0.1)
The proposed schedule for 79.0.* rollout is as follows:
July 2: Firefox Beta 79.0.0 to 10%
July 3: Firefox Beta 79.0.0 to 100%
Firefox Beta 79.0.1 to 50%

Comment 1

[Ryan VanderMeulen [:RyanVM]]

Release: 79.0.0-beta.4

seconds ago: Started rollout at 10.00% across all countries.

Comment 2

[Chenxia Liu [:liuche]]

We got a yellow-signoff from QA with one outstanding bug https://github.com/mozilla-mobile/fenix/issues/11875 but we decided that it would be acceptable to ship with to Beta while we find a fix for it on Nightly.

So here's the shipping:

July 2 (today):

• 79.0.0-beta.4 optimized O2 to 10% rollout dropped this to 1% so we don't downgrade users from optimized to unoptimized

July 3:

• sebastian will make a new AC build 79.0.0-beta.5 unoptimized 0z, and create a new 79.0.0-beta.5 with that
• roll out 79.0.0-beta.4 to 100%, and then 79.0.0-beta.5 unoptimized 0z to 50%

Comment 3

[Ryan VanderMeulen [:RyanVM]]

Rollout dropped to 1% per Slack discussion with liuche and esmyth.

Comment 4

[Sebastian Kaspari (:sebastian; :pocmo)]

I released AC 48.0.3, using GV 79.0.20200629163142 today. Then I created a 79.0.0-beta.5 that is now available in Google Play for promotion to production.

Comment 5

[Julien Cristau [:jcristau]]

79.0.0-beta.4: Full rollout.
79.0.0-beta.5: Started rollout at 50.00% across all countries.

Comment 6

[Chenxia Liu [:liuche]]

We'll be doing a dot release for 79, and Sebastian will be making 2 more Firefox Beta builds so we can continue the experiment.

Summary of dot release here: https://docs.google.com/document/d/1Gblk4KTx4us0MzMWi0zrVvh3MzvozfzvpYoOtCoD1dM/edit#

Assuming the two versions are beta.6 and beta.7, these should be rolled out 50/50 as before.:
79.0.0-beta.6 w/ O2 (optimized) to 100%
79.0.0-beta.7 w/ Oz (unoptimized) to 50%

Comment 7

[Sebastian Kaspari (:sebastian; :pocmo)]

We created two builds today that are available in Google Play for promotion to the release audience:

• 79.0.0-beta.6 using AC 48.0.4 (with optimized GeckoView 79.0.20200713203149)
• 79.0.0-beta.7 using AC 48.0.5 (with unoptimized GeckoView 79.0.20200713185329)

Flagging Eric Smyth here since he had input on the best timing for publishing those builds (so that we do not mess up our experiment data).

Comment 8

[Arturo Mejia [:amejia]]

Is there away to confirm if 79.0.20200713203149 and 79.0.20200713185329 contain this patch?, I think the patch could have a regression. If it contains the patch

Comment 9

[Ryan VanderMeulen [:RyanVM]]

They do, yes.

Comment 10

[esmyth]

I have no specific request for timing for publishing the builds.

Comment 11

[Arturo Mejia [:amejia]]

After a 2 hours of intensive testing. I couldn't find any conclusive answer, if the default headers are affecting or not downloads on the site ADP.
In some cases the site downloads works constantly with the default headers and all of the sudden the site starts to return a HTTP 500 error and removing the default header fixes the issue but if I add the default header back the site continues working.

What's appears to me it that the site it's not reliable as it doesn't behave in deterministic way with or without default headers. It could be due to traffic or other server issues.

Other sites like Gmail behaves as expected with/without default headers.

After deeper testing it looks like the issue it's more related to the website no to default headers or the gv patch I think we can proceed with Firefox Beta 79.0.0 Release as it is.

I filed #7719 to discuss the use of default header on ac.

Comment 12

[Arturo Mejia [:amejia]]

Attachment: adp_500.png

Comment 13

[Chenxia Liu [:liuche]]

Since we're not seeing any clear problems with the Downloads change, we'll plan to keep that in.

There's a Search Engine fix that we'd like to get in if QA finds that it fixes the issue: https://github.com/mozilla-mobile/fenix/issues/12544

So the plan here is:

• QA will verify the issue on Nightly https://github.com/mozilla-mobile/fenix/pull/12548

• If it's verified, Sebastian will uplift and cut 2 new releases:

  79.0.0-beta.8 using AC 48.0.4 (with optimized GeckoView 79.0.20200713203149)
  79.0.0-beta.9 using AC 48.0.5 (with unoptimized GeckoView 79.0.20200713185329)

• Relman in EST am can do the 50/50 release of this dot release (either using the beta.8 and 9, or if the fix wasn't verified, using the existing beta.6 and 7)

Comment 14

[Sebastian Kaspari (:sebastian; :pocmo)]

(In reply to Chenxia Liu [:liuche] from comment #13)

So the plan here is:

• QA will verify the issue on Nightly https://github.com/mozilla-mobile/fenix/pull/12548

• If it's verified, Sebastian will uplift and cut 2 new releases:

  79.0.0-beta.8 using AC 48.0.4 (with optimized GeckoView 79.0.20200713203149)
  79.0.0-beta.9 using AC 48.0.5 (with unoptimized GeckoView 79.0.20200713185329)

The issue was verified as fixed and both those builds are now available on Taskcluster and on Google Play (to be released by relman).

Comment 15

[Ryan VanderMeulen [:RyanVM]]

QA sent the signoff for the new Beta builds and 79.0.0-beta.8 is now at full rollout and 79.0.0-beta.9 is at 50% on top of that.

Comment 16

[Julien Cristau [:jcristau]]

We're now on 79.1.0-beta.1, closing this.