Releng & Git - Project Overview
This is the first in a series of posts about the “support git in releng” project. The goal of this project, as stated in bug 713782, is:
… The idea here is to see if we can support git in Mozilla’s RelEng infrastructure, to at least the same standard (or better) as we already currently support hg.
My hope is that blog posts will be a better forum for discussion than the tracking bug 713782, or a wiki page, at this stage.
These posts will highlight the various issues, so that the vague definitions above become clear, as do the intermediate steps needed to achieve completion.
The Ideal Future
[Refer to the main page for additional context.]
Based on discussions to date, everyone seems to have similar ideas about what “supporting git for releng” means. Later posts will highlight the work needed to ensure the ideal can be achieved, and how to arrive there.
For this post, I intend to limit the viewpoint and scope to that of the developer impact. Release notions (such as “system of record”) and scaling issues won’t be mentioned here. (N.B. Those concerns will be a key part of the path to verifying feasibility, but do not change the goal.)
As a reminder, I’m just talking about repositories that are used to produce products. [1]