How we use Git, part 2

[Randall S. Becker]

On: 25/11/15 09:30 Gervase Markham wrote:
>On 25/11/14 14:22, David Lawrence wrote:
>> Sounds fine to me. I would even go a little further and name it 
>> bug-218917-gerv or feature-218917-gerv. For people who want to 
>> contribute that do not have checkin rights, there is always github as well and they can use similar naming there.
>When would you choose "bug" and when "feature"? How is expressing that distinction in the branch name useful?
>Or do you just think it reads better?

I prefer task_218917_gerv, to be perfectly frank. For most commits, I put in the Bugzilla URL anyway (Mylyn does it automagically), so looking up the details of the bug or feature is really not far. I do not really like a purely numeric prefix, as this can be a little confusing between branches and abbreviated git versions if you are looking at change trees. Having some standard prefix that says "this branch is something I'm doing because I'm changing something deliberately" is a good visual clue in branch management - as opposed to "this branch is here because I'm trying to piece things in my repository back together" or "we're on the road to a release". I realize this is close to the realm of variable name coding standards, and probably a nano-quibble, but having a meaningful prefix, for me, is desirable.

Just my $0.016,
Randall