IT/Maintenance/DevServices: Difference between revisions

Jump to navigation Jump to search
Line 15: Line 15:
The schedule mimics the 6-week release cycle.   
The schedule mimics the 6-week release cycle.   


Mozilla IT will work with Release Coordinators to ensure there aren't any external events that should preempt the Standing Windows.
{| class="fullwidth-table"
|-
! Week 1
! Status
|-
| Monday || Merge day
|-
| Tuesday || Ship Release
|-
| Thursday || Ship Beta
|-
| Friday || Aurora enabled
|-
|}


Week 1
* Merge day on Monday
* Release ships on Tuesday
* Beta ships on Thursday
* Aurora enabled on Friday


* Requires bug with
Week 2
** documented action plan
* Usually decide by Wednesday whether to ship a .1 release
** roll-back plan before
* If a .1 release is necessary, typically release by Friday
* Standing Window:
 
Week 3
* A .1 is sometimes released as late as Monday (as with the mobile 15.0.1)
* Tuesday onwards should be clear
 
Week 4 & 5
* Clear
 
Week 6
* Preferable not to make major changes, as we're chasing down release issues and building a release candidate


= Notifications =  
= Notifications =  
Confirmed users, Bureaucrats and Sysops emeriti
1,081

edits

Navigation menu