-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Releng Firefox Beta 79.1.0 #12761
Comments
Tried to pin to AC 50.0.0 from last week, but it seems like 51.0.0 has added a ton of breaking changes so we'll wait for the AC 51.0.0 release on Tuesday cc @pocmo - since this was cut in the morning, AC 51.0.0 should apply cleanly. In the future, we'll be ending our sprints on Wednesday EOD, so we should be able to pick the freshest AC at the end of every sprint 🥬 |
AC 51.0.0 is now released and available. But there's something odd about the versioning here. This is a new branch that will be cut from It also gets confusing with the release version: We are going to release 79.0.0 to the fennec release audience soon. If we need to follow-up with a dot release to fix something then this would be 79.0.1 - which then would be something completely different than 79.0.1-Beta that we build here. This is very confusing. This also is somehow misleading with semantic versioning: This is not a patch version with "backwards compatible bug fixes.". We can't really change the major version while it is syncrhonized with Gecko(View). But maybe we should bump the minor version here instead and turn this into |
Rolled out to 100% last week. |
This build is currently using 79.0.0 Beta, but 80 will go to Beta later this week. If we want to update, we can push a new version.
Beta Builds
Monday, July 20 Firefox Beta build w/ AC 50.0.0Tuesday, July 21 Firefox Beta build w/ AC 51.0.0During Beta Product Integrity (Beta Release until PI green signoff)
During Production Release Rollout [Tuesday, Wednesday following Monday Release Day]
Room for improvement
eng:qa:needed
to issues Automate some manual parts of Releng Checklist #6199signing-production
task look likepublic/build/arm64-v8a/geckoBeta/target.apk
. This means that the dev must download, then rename them by hand. Could RM update these to generatepublic/build/arm64-v8a/geckoBeta/firefox-preview-v3.0.0-rc.1-arm64-v8a.apk
, or similar?┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: