UX Branch: Difference between revisions

Jump to navigation Jump to search
315 bytes removed ,  26 September 2011
Line 19: Line 19:
* 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.
* 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.
* Your patch should not cause test failures on the [http://tbpl.mozilla.org/?tree=UX UX branch TBPL]. Patches that cause unaddressed test failures will be backed out after 24 hours.
* While patches that are works-in-progress can have known issues and still land on the UX branch, they should not cause the UX branch to fail to compile or be unable to perform the basic functions of a browser.


== What if I have questions? ==
== What if I have questions? ==


You can ask for help in #ux on irc.mozilla.org.
You can ask for help in #ux on irc.mozilla.org.
Confirmed users
1,111

edits

Navigation menu