ReleaseEngineering:ProjectBranchPlanning: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 6: Line 6:
** Your project name will also be used for the repo name (eg: hg.mozilla.org/projects/jaegermonkey) - please state if you have an existing repo you're looking to use instead of a newly created repo.
** Your project name will also be used for the repo name (eg: hg.mozilla.org/projects/jaegermonkey) - please state if you have an existing repo you're looking to use instead of a newly created repo.
** Note: project names should avoid using confusing/overloaded terms, like "build", "firefox", "release"...
** Note: project names should avoid using confusing/overloaded terms, like "build", "firefox", "release"...
** Note: Repos for finite-duration project branches will go into [http://hg.mozilla.org/projects http://hg.mozilla.org/projects]. Repos for never-ending team/integration branches will go into [http://hg.mozilla.org/integration http://hg.mozilla.org/integration"].
** Note: Repos for finite-duration project branches will go into [http://hg.mozilla.org/projects http://hg.mozilla.org/projects]. Repos for never-ending team/integration branches will go into [http://hg.mozilla.org/integration http://hg.mozilla.org/integration].


* For builds:
* For builds:
Confirmed users
2,679

edits