Release Management/Release Process Checklist Documentation: Difference between revisions

Release Management/Release Process Checklist Documentation (view source)

59 bytes added , 17 July 2024

Add steps around automated Android betas

383

edits

@@ Line 259: / Line 259: @@
 ## Click Enable
 ##* [[File:Screen Shot 2022-06-01 at 9.47.26 AM.png|thumb|center|middle]]
-##  Perform the same actions for Firefox Developer Edition: Beta
+##  Perform the same actions for Firefox Developer Edition: Beta and Firefox Android (Android-Components, Fenix, Focus): Beta
-#* Please Note: Automated Betas are built at 21:00 UTC every Sunday, Tuesday, and Thursday as determined [https://hg.mozilla.org/releases/mozilla-beta/file/default/.cron.yml#l17 here].
+#* Please Note: Automated Betas are built at 13:00 UTC every Monday, Wednesday, and Friday as determined [https://hg.mozilla.org/releases/mozilla-beta/file/default/.cron.yml#l17 here].
 # Make the Beta release notes public in Nucleus
 #* Enable the Is Public checkbox and save
@@ Line 333: / Line 333: @@
 #* Taskcluster email: “firefox xx.0bx build1/mozilla-beta is in the candidates directory”
 #* Taskcluster email: “devedition xx.0bx build1/mozilla-beta is in the candidates directory”
-# Create Firefox Android (AC, Fenix, Focus) release in Ship-It
+# Confirm the Firefox Android (AC, Fenix, Focus) builds have started
-# Start Firefox Android (AC, Fenix, Focus) release in Ship-It via Promote
+#* Taskcluster email: “Build of firefox-android xx.0bx build 1"
 # Confirm notification sent when the Firefox Android (AC, Fenix, Focus) builds finish
 #* Taskcluster email: “firefox-android xx.0bx build1/mozilla-beta is in the candidates directory"