canmove, Confirmed users
2,850
edits
ReleaseEngineering/Day 1 Checklist: Difference between revisions
→Mercurial (hg)
(add links) |
ChrisCooper (talk | contribs) |
||
| Line 133: | Line 133: | ||
There is an excellent step-by-step guide for setting up and using hg: [https://mozilla-version-control-tools.readthedocs.org/en/latest/hgmozilla/index.html Mercurial for Mozillians] | There is an excellent step-by-step guide for setting up and using hg: [https://mozilla-version-control-tools.readthedocs.org/en/latest/hgmozilla/index.html Mercurial for Mozillians] | ||
The root webview of the Mozilla hg repositories is here: https://hg.mozilla.org/ | |||
Most releng code lives in repos under https://hg.mozilla.org/build | |||
There are 3 levels of commit access: | |||
* Level 1 access allows you to use the [[ReleaseEngineering/TryServer|Try Server]] and setup user repos. As a new contributor, you should request this on day one. | |||
* Level 2 access is required to land code in the build and project repos. Once you have a proven track record of successful patches, you can ask your manager/mentor to vouch for your Level access. Your manager/mentor can also land patches for you until you receive Level 2 access is enabled. | |||
* Level 3 access is required to land code directly on [https://hg.mozilla.org/mozilla-central mozilla-central] and its derived release branches. At some point in your Mozilla contribution story, you may need Level 3 access but many contributors never do. Talk to your manager/mentor if you think you need this access. You should already have Level 2. | |||
You need to file an IT bug to get hg commit access. Follow the instructions for [https://www.mozilla.org/en-US/about/governance/policies/commit/ Becoming a Mozilla Committer], and for Level 2, specify you need access to (at least) hg.mozilla.org/build/* (Product/Component: mozilla.org/Repository Account Requests). | |||
* example request: {{bug|703351}} | |||
== Git & Github == | == Git & Github == | ||