EngineeringProductivity/HowTo/MirrorRepo: Difference between revisions

EngineeringProductivity/HowTo/MirrorRepo (view source)

16 bytes added , 12 September 2012

947

edits

@@ Line 5: / Line 5: @@
 The reasoning is that tools and harnesses such as these are useful or required for Mozilla's test infrastructure, but are also useful as standalone utilities. Keeping them in standalone repositories gives us greater development freedom, makes it easier for new contributors to help out and makes the tools more visible to people outside of the Mozilla community.
-== Steps ==
+== Steps to mirror mozbase ==
-This guide uses git [http://learn.github.com/p/tagging.html tags] which are simply a way to assign a name to a commit. This tutorial will use mozbase as an example, though the workflow can apply to any project. Now suppose you fix a critical bug, or add a major new feature that is needed by the test infrastructure in Mozilla-Central (herein called m-c).
+This methodology uses git [http://learn.github.com/p/tagging.html tags] which are simply a way to assign a name to a commit. If you fix a critical bug, or add a major new feature that is needed by the test infrastructure in mozilla-central, you'll want to mirror the fix from https://github.com/mozilla/mozbase to http://hg.mozilla.org/mozilla-central .
 # Write your patch for mozbase, attach it to your bug, get it reviewed, check it in to master and resolve the bug fixed [https://wiki.mozilla.org/Auto-tools/Projects/MozBase#Working_on_MozBase_and_contributing_patches as normal]. Now it is time to mirror the latest master to m-c.