Gaia/UX Branch/Maintenance: Difference between revisions

Gaia/UX Branch/Maintenance (view source)

10 bytes removed , 11 December 2012

canmove, Confirmed users

227

edits

@@ Line 10: / Line 10: @@
 * Update UX Branch Daily
 * Review pull requests 2-3 times a week
-  * Open bug in Bugzilla
+** Open bug in Bugzilla
-  * Add Status Whiteboard "uxbranch" (if it doesn't have the tag already)
+** Add Status Whiteboard "uxbranch" (if it doesn't have the tag already)
-  * Review patch, understand risk-level of patch
+** Review patch, understand risk-level of patch
-  * Apply patch locally and test on-device
+** Apply patch locally and test on-device
-  * If all is OK, merge pull request.
+** If all is OK, merge pull request.
-  * Only one commit per fix! Make sure commit has bug # and details. If necessary, apply as patch and fix commit message.
+** Only one commit per fix! Make sure commit has bug # and details. If necessary, apply as patch and fix commit message.
-  * Add Status Whiteboard "landed in uxbranch"
+** Add Status Whiteboard "landed in uxbranch"
 * Create a pull request for qa-verified bugs every week.
-  * Cherry pick commits verified by QA and merged into UX, but not yet in master. Prefer cherry-picking the original commit instead of the merge commit.
+** Cherry pick commits verified by QA and merged into UX, but not yet in master. Prefer cherry-picking the original commit instead of the merge commit.
-  * Issue pull request.
+** Issue pull request.
-  * Include links to bugs in pull request message.
+** Include links to bugs in pull request message.
 Good news: cherry pick should fail noisily if it can't merge properly.