816
edits
Gaia/UX Branch: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(→Etiquette: Added link to github tutorial on rebase.) |
No edit summary |
||
| Line 1: | Line 1: | ||
== | = V1 UX Branch = | ||
==== Background: ==== | |||
As of Nov 8, it has been hard to get UX fixes into `mozilla-b2g/gaia` because engineers are trying hard to get stability up and bug counts down. UX improvements/fixes are difficult to get merged because the review process is focused first on blocking and broken issues. | As of Nov 8, it has been hard to get UX fixes into `mozilla-b2g/gaia` because engineers are trying hard to get stability up and bug counts down. UX improvements/fixes are difficult to get merged because the review process is focused first on blocking and broken issues. | ||
As a temporary approach, we've set up a UX branch at https://github.com/gordonbrander/gaia/tree/ux to keep the needle moving forward on UX fixes. Engineering can cherry-pick fixes from this branch into master. The goal is to show a significant improvement in this branch and to get QA signing off on it. | As a temporary approach, we've set up a UX branch at https://github.com/gordonbrander/gaia/tree/ux to keep the needle moving forward on UX fixes. Engineering can cherry-pick fixes from this branch into master. The goal is to show a significant improvement in this branch and to get QA signing off on it. | ||
==== How: ==== | |||
* Primary: get bugs flagged blocking+ and dev assigned. | |||
* Secondary: for bugs that do not qualify as blocking+, prioritize and build on UX branch, then apply to merge to main branch. | |||
==== High level process for UX branch: ==== | |||
1. Identify bugs | |||
2. Patryk + Steve triage to nom as blocking+, and prioritize the non-blockers. | |||
3. Submit patches for prioritized patches | |||
4. QA test | |||
5. Pull request once weekly | |||
== Setting up the UX Branch == | == Setting up the UX Branch == | ||