couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benoit Chesneau <bchesn...@gmail.com>
Subject Re: [VOTE] Git Commit Messages
Date Thu, 18 Jul 2013 18:12:54 GMT
On Thursday, July 18, 2013, Noah Slater wrote:

> Benoit, your concerns are orthogonal to the location of the documentation.
>
>
my concern is not about the doc but about the news and changes files that
have been removed. cf the thread about it.





> Dirkjan, thanks for taking care of this! Long overdue.
>
>
> On 18 July 2013 13:29, Benoit Chesneau <bchesneau@gmail.com <javascript:;>>
> wrote:
>
> > On Thu, Jul 18, 2013 at 2:21 PM, Dirkjan Ochtman <dirkjan@ochtman.nl<javascript:;>
> >
> > wrote:
> >
> > > On Mon, May 27, 2013 at 5:42 PM, Robert Newson <rnewson@apache.org<javascript:;>
> >
> > wrote:
> > > > I'd like to vote on two questions;
> > > >
> > > > 1) That we adopt the git commit message guidelines above.
> > > > 2) That we delete NEWS/CHANGES from master before the next release
> > after
> > > 1.3.1.
> > > >
> > > > The voting rules are lazy consensus with a 72 hour waiting period.
> You
> > > > do not have to vote if you agree, though you are welcome to do so. If
> > > > you do vote against I encourage you to include a constructive reason
> > > > or suggest an alternative.
> > >
> > > Based on the votes for proposal 2 (+1 all around, one abstainment),
> > > I'm going to delete NEWS and CHANGES from master and make sure the
> > > limited stuff is there now is instead reflected in the docs release
> > > history chapter.
> > >
> > > Cheers,
> > >
> > > Dirkjan
> > >
> >
> > well if i reread the thread, the question was retracted..... imo for 1,4,
> > the best idea is to extract the logs from the commit and add them on top
> pf
> > the changes.
> >
> > - benoit
> >
>
>
>
> --
> NS
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message