The canonical commit/push/land cycle at Mozilla
[This is an experiment in publishing a doc piece by piece as blog entries. Please refer to the main page for additional context.]
Untangling the terminology
In the old days, before DVCS, “commit” only had only one real purpose. It was how you published your work to the rest of the world (or your project’s world at least). With DVCS, you are likely committing quite often, but still only occasionally publishing.
Changes to commit workflow
[This is an experiment in publishing a doc piece by piece as blog entries. Please refer to the main page for additional context.]
With all the changes to support git, how will that affect a committer’s workflow? (For developer impact, see this post.)
The primary goal is to work within the existing Mozilla commit policy [1]. Working within that constraint, the idea is “as little as possible”, and this post will try to describe how big “as little” is.
Remember: all existing ways of working with hg will continue to work! These are just going to be some additional options for folks who prefer to use github & bitbucket.