couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <>
Subject Re: [PROPOSAL] tag our commits
Date Wed, 04 Dec 2013 12:36:43 GMT
>From a procedural perspective, the way this should work is that things
which reach a broad consensus via discussion should be added to the
draft workflow doc. Anything that seems contentious should be
discussed until it looks like we have consensus. Once the draft is
finished, we do one vote to tie a bow on it, and the whole thing
becomes official.

If someone wants to run with this, please reach out to me and I can
guide you personally on how to approach this from a project

On 4 December 2013 13:34, Noah Slater <> wrote:
> Hi folks,
> This sounds like a good idea, but I have a request.
> We are still waiting for someone to run with the idea of writing up
> our Git workflow. This should document how we use Git on the project.
> How to make feature branches. How to manage release branches. And...
> *drumroll* how to tag commits.
> There's a lot of undocumented rules and I have heard first hand from
> people that it is intimidating trying to figure out how to contribute
> to the project. So this work would be very valuable for the community.
> On 30 November 2013 10:45, Dave Cottlehuber <> wrote:
>> Great, let's do it. Before merging, all we'll need to do is get a +1
>> from another dev & we're good to go.
>> On 30 November 2013 10:23, Benoit Chesneau <> wrote:
>>> On Tue, Oct 29, 2013 at 9:29 AM, Benoit Chesneau <>wrote:
>>>> My only objection to the `tag:` fomat is that this is not the way you tag
>>>> an email generally. Since the first line of the commit is generally the
>>>> subject of the message and the patch you get with format-patch, I think
>>>> that using a common way to tag the subject may be better.
>>>> I really don't think that's weird for those who are mainly using the mail
>>>> to handle the git commits and some are.
>>>> Maybe that worth to take it in consideration?
>>> I just rad last changelog fron the linux kernel [1], and as you can see the
>>> tags are <tag>: ... on the firstline, in lowercase or uppercase. So let's
>>> go for that indeed.
>>> Also I quite like their changelog. Much more precise than our changelog.
>>> Maybe we could follow such idea.
>>> - benoit
>>> [1]
> --
> Noah Slater

Noah Slater

View raw message