UX Branch: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(14 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== What is the UX branch? ==
== What is the UX branch? ==
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 would 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.
=== 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? ==
== 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 along with a [https://developer.mozilla.org/en-US/docs/Developer_Guide/Source_Code/Mercurial/Bundles bundle] for more efficient clones at http://ftp.mozilla.org/pub/mozilla.org/firefox/bundles/ux.hg


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/. You can use http://msuja.ws/ux as a more friendly URL to share.


== What are the rules for the UX branch? ==
== What are the rules for the UX branch? ==
 
* When a patch for the UX branch is checked in, the bug's whiteboard should be updated with the phrase '[ux-branch]' (minus the single quotes).
* When you land a patch, add it to the [http://etherpad.mozilla.com:9000/ux-branch 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 [http://tbpl.mozilla.org/?tree=UX UX branch TBPL] you can monitor.
* 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 or #fx-team on irc.mozilla.org. Particularly, you may want to message the following people on IRC: mconley, jaws, MattN, Gijs, Unfocused, mikedeboer, or shorlander.

Latest revision as of 19:04, 10 January 2014

What is the UX branch?

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 would 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 along with a bundle for more efficient clones at http://ftp.mozilla.org/pub/mozilla.org/firefox/bundles/ux.hg

Nightly builds are available at: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-ux/. You can use http://msuja.ws/ux as a more friendly URL to share.

What are the rules for the UX branch?

  • When a patch for the UX branch is checked in, the bug's whiteboard should be updated with the phrase '[ux-branch]' (minus the single quotes).

What if I have questions?

You can ask for help in #ux or #fx-team on irc.mozilla.org. Particularly, you may want to message the following people on IRC: mconley, jaws, MattN, Gijs, Unfocused, mikedeboer, or shorlander.