Confirmed users
313
edits
UX Branch: Difference between revisions
→What is the UX branch?
| 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.}} | {{Note|The UX Branch is currently reserved for Australis dogfooding. Only finalized and reviewed Australis patches to merge to mozilla-central should land here.}} | ||
The UX branch is a project branch for landing experimental UX changes before they are ready to land on mozilla-central. Developers | The UX branch is historically a project branch for landing experimental UX changes before they are ready to land on mozilla-central. Developers could 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. | ||
Presently, the UX branch is used as a future feeder for mozilla-central, so all previous UX-branch rules are set aside, and the UX branch follows the normal mozilla-central process. | |||
=== Can I use my clone of mozilla-central to write patches for the UX branch? === | === 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 ;-)'' | 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 ;-)'' | ||