|
|
| Line 42: |
Line 42: |
| *[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=quality.mozilla.org&target_milestone=1.0 1.0] | | *[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=quality.mozilla.org&target_milestone=1.0 1.0] |
| **Pushed July 16 | | **Pushed July 16 |
|
| |
| == Release Guidelines ==
| |
| === Definitions ===
| |
| * Milestone release = a release made up of any number of bugs that are part of a goal for QMO
| |
| * Security release = a small and quick release made up of security bugfixes ONLY. A security release is not part of the milestone releases (no milestone number is required here)
| |
| * Push = pushing the code changes from the SVN production branch to the live site.
| |
|
| |
| === Best Practice ===
| |
| * Security related bugs are committed to stage, verified, committed to production and pushed as quickly as possible.
| |
| * Regular (not security related) bugs are only committed to stage at first.
| |
| ** Drupal has fairly frequent security releases. To make it quick and easy for those to be pushed live when they come out, other bugfix code should not be committed to production until it is ready for the milestone release.
| |
| * Bugs are verified on stage before the push
| |
| * Code from verified bugs is committed to production on (or very close) to push date
| |
| * Bugs are re-verified on production after the push
| |
| * Bugs that have not been committed to production are postponed to the next milestone
| |
|
| |
|
| |
|
| == QMO meeting notes == | | == QMO meeting notes == |