corysanin/tubestation
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

No bug - Update Firefox Pocket Guide to reflect updated QA milestones. DONTBUILD

Browse Source 
Differential Revision: https://phabricator.services.mozilla.com/D231159
This commit is contained in:
Ryan VanderMeulen
2024-12-04 22:29:24 +00:00
parent da3aec8498
commit 30de208496
1 changed files with 25 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
docs/contributing/pocket-guide-shipping-firefox.rst
View File

@@ -151,21 +151,23 @@ a quality and compelling product will be consistently delivered to our
users with each new version. See below for a distilled list of those
milestones.
=========================================== ================ ================= ===============================================================================
===================================================== ================ ================= =======================================================================================
Milestone Week Day of Week
------------------------------------------- ---------------- ----------------- -------------------------------------------------------------------------------
----------------------------------------------------- ---------------- ----------------- ---------------------------------------------------------------------------------------
QA Request & Feature technical documentation deadline Nightly W0 Friday QA feature testing should be requested prior to the start of the Nightly cycle
Merge Day Nightly W1 Monday Day 1 of the new Nightly Cycle
PI Request deadline Nightly W1 Friday Manual QA request deadline for high risk features
Feature technical documentation due Nightly W2 Friday Deadline for features requiring manual QA
Beta release notes draft Nightly W4 Wednesday
Feature Complete Milestone Nightly W2 Friday Last day to land risky patches and/or enable new features
QA Test Plan approval due Nightly W2 Friday Last day to provide QA with feature Test Plan sign-offs
Nightly features Go/No-Go decisions Nightly W4 Wednesday
Feature Complete Milestone Nightly W4 Thursday Last day to land risky patches and/or enable new features
Beta release notes draft Nightly W4 Wednesday
Nightly soft code freeze start Nightly W4 Thursday Stabilization period in preparation to merge to Beta
QA Test Plan approval due Nightly W4 Friday Last day to provide QA with feature Test Plan sign-offs
String freeze Nightly W4 Friday Modification or deletion of strings exposed to the end-users is not allowed
QA pre-merge regression testing completed Nightly W4 Friday
String freeze Nightly W4 Friday Modification or deletion of strings exposed to the end-users is not allowed
Merge Day Beta W1 Monday Day 1 of the new Beta cycle
Pre-release sign off Beta W3 Friday Final round of QA testing prior to Release
User affecting changes identified & provided to SUMO Beta W1 Friday
End of Early Beta & intended pref state deadline Beta W2 Friday Post-B6
Pre-release sign off Beta W3 Wednesday Final round of QA testing prior to Release
Go/No-Go for features riding train Beta W3 Friday
Firefox RC week Beta W4 Monday Validating Release Candidate builds in preparation for the next Firefox Release
Release Notes ready Beta W4 Tuesday
What’s new page ready Beta W4 Wednesday
@@ -173,7 +175,7 @@ Firefox go-live @ 6am PT Release W1 Tuesday D
Firefox Release bump to 100% Release W1 Thursday Increase deployment of new Firefox Release to 100% of Release users
Scheduled dot release approval requests due Release W2 Friday All requests required by EOD
Scheduled dot release go-live Release W3 Tuesday By default, ships when ready. Specific time available upon request.
=========================================== ================ ================= ===============================================================================
===================================================== ================ ================= =======================================================================================
The Release Management team (aka “Relman”) monitors and enforces this