UX Branch: Difference between revisions
Jump to navigation
Jump to search
(Created page with "== What is the UX branch? == The UX branch is a project branch for landing experimental UX changes to mozilla-central. Developers can land un-reviewed patches on this branch to g...") |
|||
| Line 13: | Line 13: | ||
* If you iterate on your patch, you should backout your original changeset and re-land a new patch. This makes patches easy to track and prepares them for the normal review process. | * If you iterate on your patch, you should backout your original changeset and re-land a new patch. This makes patches easy to track and prepares them for the normal review process. | ||
* When you push to the UX branch, you should be a good citizen and merge mozilla-central into the branch. | * When you push to the UX branch, you should be a good citizen and merge mozilla-central into the branch. | ||
* Backout your patch when it lands on mozilla-central. | |||
* Since this branch is experimental, you do not need to make sure all tests pass, but it would be in your best interest to fix your patch, since a broken patch won't be able to land on mozilla-central later. There is a [http://tbpl.mozilla.org/?tree=UX UX branch TBPL] you can monitor. | * Since this branch is experimental, you do not need to make sure all tests pass, but it would be in your best interest to fix your patch, since a broken patch won't be able to land on mozilla-central later. There is a [http://tbpl.mozilla.org/?tree=UX UX branch TBPL] you can monitor. | ||
Revision as of 17:27, 23 June 2011
What is the UX branch?
The UX branch is a project branch for landing experimental UX changes to mozilla-central. Developers can land un-reviewed patches on this branch to gather feedback from users and work with the UX team to iterate on UX design. After a final design is reached, patches must go through the normal review process before landing on mozilla-central.
Where is the UX branch?
http://hg.mozilla.org/projects/ux
What are the rules for the UX branch?
- When you land a patch, add it to the UX branch etherpad. You should include:
- Your name
- Bug number
- Changeset link
- Any additional comments
- If you iterate on your patch, you should backout your original changeset and re-land a new patch. This makes patches easy to track and prepares them for the normal review process.
- When you push to the UX branch, you should be a good citizen and merge mozilla-central into the branch.
- Backout your patch when it lands on mozilla-central.
- Since this branch is experimental, you do not need to make sure all tests pass, but it would be in your best interest to fix your patch, since a broken patch won't be able to land on mozilla-central later. There is a UX branch TBPL you can monitor.