UX Branch: Difference between revisions

Jump to navigation Jump to search
227 bytes added ,  18 April 2013
Update for Austrlis
(Update for Austrlis)
Line 1: Line 1:
== What is the UX branch? ==
== What is the UX branch? ==
 
{{Note|The UX Branch is currently reserved for Australis dogfooding. Only finalized and reviewed Australis patches to merge to mozilla-central should land here. Some of the info below doesn't currently apply.}}
The UX branch is a project branch for landing experimental UX changes before they are ready to land on mozilla-central. Developers can use this branch to gather feedback on un-reviewed patches 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.
The UX branch is a project branch for landing experimental UX changes before they are ready to land on mozilla-central. Developers can use this branch to gather feedback on un-reviewed patches 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? ==
== Where is the UX branch? ==


The hg repository is available at: http://hg.mozilla.org/projects/ux
The hg repository is available at: https://hg.mozilla.org/projects/ux


Nightly builds are available at: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-ux/
Nightly builds are available at: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-ux/


== What are the rules for the UX branch? ==
== What are the rules for the UX branch? ==
Line 16: Line 16:
** Changeset link
** Changeset link
** Any additional comments
** 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.
* <s>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.</s>
* When you push to the UX branch, you should be a good citizen and merge mozilla-central into the branch.
* <s>When you push to the UX branch, you should be a good citizen and merge mozilla-central into the branch.</s>
* Back out your patch when it lands on mozilla-central.
* Back out your patch when it lands on mozilla-central.
* 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.
* Your patch should not cause test failures on the [https://tbpl.mozilla.org/?tree=UX UX branch TBPL]. Patches that cause unaddressed test failures will be backed out after 24 hours.


== 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
933

edits

Navigation menu