Confirmed users
583
edits
ReMo Mozilla Reps/Release Process: Difference between revisions
no edit summary
(Created page with "=== Purpose === The purpose of this release process is to ensure that only high-quality code moves into production and does so in an orderly, predictable way that all stakehol...") |
No edit summary |
||
| Line 5: | Line 5: | ||
reps.mozilla.org releases go to production when significant code is ready for release. Releases may happen as often as weekly; they may be less frequent in some cases. In order for a particular change to land in a release... | reps.mozilla.org releases go to production when significant code is ready for release. Releases may happen as often as weekly; they may be less frequent in some cases. In order for a particular change to land in a release... | ||
* it should be described in a bug | * it should be described in a bug | ||
* the bug should have a | * the bug should have a version set for a future release | ||
* the bug should be deployed to staging by noon on the day prior to the release | * the bug should be deployed to staging by noon on the day prior to the release | ||