UX Branch: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 14: Line 14:


== What are the rules for the UX branch? ==
== What are the rules for the UX branch? ==
 
* The UX branch is currently being used as a staging ground for the upcoming Australis feature set.
* When you land a patch, add it to the [http://etherpad.mozilla.com:9000/ux-branch UX branch etherpad]. You should include:
* All patches that land on the UX branch need to follow the same review process that patches destined for mozilla-central need to follow.
** Your name
* When a patch for the UX branch is checked in, the bug's whiteboard should be updated with the phrase '[fixed-in-ux]' (minus the single quotes).
** Bug number
** You can refer to https://people.mozilla.com/~mnoorenberghe/australis/ for the Australis dashboard to see which bugs have higher priorities and the status of all Australis bugs. This site is recommended as it treats [fixed-in-ux] bugs as fixed, whereas generic Bugzilla queries won't.
** Changeset link
** Any additional comments
* <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>
* <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.
* 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.

Revision as of 16:22, 28 October 2013

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.


Can I use my clone of mozilla-central to write patches for the UX branch?

No, this is not a recommended approach to working on the UX branch. You should instead clone the UX repository. While anything is possible, using mozilla-central to contribute patches for UX will introduce more work and increased chances of things going wrong. It's just not worth it ;-)

Where is the UX branch?

The hg repository is available at: https://hg.mozilla.org/projects/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?

  • The UX branch is currently being used as a staging ground for the upcoming Australis feature set.
  • All patches that land on the UX branch need to follow the same review process that patches destined for mozilla-central need to follow.
  • When a patch for the UX branch is checked in, the bug's whiteboard should be updated with the phrase '[fixed-in-ux]' (minus the single quotes).
    • You can refer to https://people.mozilla.com/~mnoorenberghe/australis/ for the Australis dashboard to see which bugs have higher priorities and the status of all Australis bugs. This site is recommended as it treats [fixed-in-ux] bugs as fixed, whereas generic Bugzilla queries won't.

What if I have questions?

You can ask for help in #ux on irc.mozilla.org.