Mobile/Firefox for iOS/Process: Difference between revisions
< Mobile | Firefox for iOS
Jump to navigation
Jump to search
No edit summary |
|||
| Line 12: | Line 12: | ||
[[File:Release_Cycle_-_High_Level.jpg|frameless|1200px]] | [[File:Release_Cycle_-_High_Level.jpg|frameless|1200px]] | ||
<div style="display: flex; flex-flow: row wrap; width: 100%;"> | |||
<div style="order: 1; flex-grow: 3; margin: 0.5em; border: 0.1em solid darkgreen; padding: 0.5em; background-color: palegreen; min-width: auto;"> | |||
At the end of the 6-week period of development, once 'Feature Complete' has been declared, a Release branch is created off of Master, containing the features designated for that release. | At the end of the 6-week period of development, once 'Feature Complete' has been declared, a Release branch is created off of Master, containing the features designated for that release. | ||
It is the release branch that is then stabilized for 4 weeks until submission. | It is the release branch that is then stabilized for 4 weeks until submission. | ||
</div> | |||
</div> | |||
[[File:Release_Milestone_Details.jpg|frameless|1200px]] | [[File:Release_Milestone_Details.jpg|frameless|1200px]] | ||
Revision as of 19:44, 18 March 2016
Firefox for iOS Rapid Release Process
A single release is composed of 6 weeks of development time, a 4 week stabilization period, and a release period of approximately** 2 weeks.
Releases overlap such that development begins on the next release when the previous release enters stabilization.
Submissions take place every 6 weeks.
At the end of the 6-week period of development, once 'Feature Complete' has been declared, a Release branch is created off of Master, containing the features designated for that release.
It is the release branch that is then stabilized for 4 weeks until submission.
