robla at wikimedia
Mar 22, 2012, 1:16 PM
Post #7 of 9
On Wed, Mar 21, 2012 at 11:17 AM, Diederik van Liere
Re: Creating naming conventions for git branches?
[In reply to]
<dvanliere [at] gmail> wrote:
> With the pending git migration upon us,is this also the right time to
> think about naming conventions for git branches or is there nu such a
Yup, there is. My bias right now, though, is that we have one single
convention, which is to prefix our branch names with the year (e.g.
"2012/bug12345"), and not overthink it too much past that. That lets
us have an implicit hierarchy that naturally fades to irrelevance over
time, since, for example, it's unlikely that in 2017 most people will
care about anything under "2012/*", so if we decide on something we
regret, we've limited the damage.
We don't have to make *all* branches like that. So, for example, we
can keep using the same convention for all of the branches that
survived the svn->git migration (e.g. REL1_17, REL1_18, REL1_19), but
new work branches should almost certainly follow the year prefix
Wikitech-l mailing list
Wikitech-l [at] lists