couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Lehnardt <>
Subject Re: branch names
Date Tue, 04 Dec 2012 18:33:49 GMT

On Dec 4, 2012, at 19:19 , Benoit Chesneau <> wrote:

> On Tue, Dec 4, 2012 at 6:55 PM, Jan Lehnardt <> wrote:
>> Hey all,
>> just a heads up, the scheme for branch names we agreed on
>> is: 1532-feature-add-docs No underscores. Please follow
>> this.
>> The fact that the cors branch doesn’t follow this is a
>> historic artefact that I thought wasn’t worth cleaning
>> up, but it looks I was wrong.
>> From now on, I will rule with an iron fist about getting
>> these details right. Current branches with diverging names
>> are exempt.
>> Cheers
>> Jan
>> --
> Actually we were agree to discuss that later a little more.

Nope, we made a decision:

that resulted in:

We can always change things as this is completely arbitrary. But we must stick
to one scheme. And I am tired of discussing this because we have a working
solution that doesn’t warrant any more bikeshedding.

> I do think we should distinct the issue number from the rest. And using an
> underscore was good for that. Not a big deal though.

The issue number is always first and an integer, the issue type is always one
of "fix", "feature", or other type we come up with that is a single word,
everything else is the short description of the issue. there are no ambiguities
and things are pleasant to read.

I’m happy to change this too all underscores, but not mixed. And we’ve been
through this and everyone who cared weighed in, so hyphens it is.

> Also something that wasn't discussed is how we distinct ticket or pr from
> github from the rest.  *If* this should be distinguished.

Please open a separate discussion on this.


View raw message