Re: [VOTE] Git Commit Messages

[Dirkjan Ochtman <di...@ochtman.nl>]

On Mon, May 27, 2013 at 5:42 PM, Robert Newson <rn...@apache.org> 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

Re: [VOTE] Git Commit Messages

[Noah Slater <ns...@apache.org>]

Oh well. No harm, no foul. The important thing is that we're making
progress and that the right work is happening. There's no indication on
this thread that anyone thinks moving NEWS and CHANGES to docs/ is a bad,
idea, and a good indication that we need to have more of a discussion about
how to maintain the actual release notes. So everything fine. :)

(FWIW, I agree with you. We should not wipe out old changelogs. They are
valuable. And the Git commit messages for that period are going to be very
poor, and not at all a good replacement.)


On 18 July 2013 19:50, Benoit Chesneau <bc...@gmail.com> wrote:

> On Thu, Jul 18, 2013 at 8:49 PM, Noah Slater <ns...@apache.org> wrote:
>
> > Well, this is a VOTE thread, so it's not the appropriate place for a
> > DISCUSSion. I think the conversation about how we maintain our release
> > notes is a very valuable one, and I would like to have that conversation.
> >
> >
> > And the vote has been aborted that's the my point. And I yes I agree we
> should start a new discussion thread.
>
> - benoit
>
>
> > On 18 July 2013 19:41, Benoit Chesneau <bc...@gmail.com> wrote:
> >
> > > On Thu, Jul 18, 2013 at 8:35 PM, Noah Slater <ns...@apache.org>
> wrote:
> > >
> > > > NEWS and CHANGES need to be moved to the docs one way or another, so
> > > Dirkan
> > > > is doing us a favour by undertaking that effort. If you'd like to
> > restart
> > > > the discussion as to how we populate our changelog, please start a
> new
> > > > thread.
> > > >
> > > >
> > > Please take the time to read this thread. Also I don't dismiss the work
> > > done by djc in any case. I am asking an honest question and you don't
> > > answer to it. Also can we continue the discussion on the right thread?
> Ie
> > > the commit one?
> > >
> > > Thanks.
> > >
> > > - benoit
> > >
> >
> >
> >
> > --
> > NS
> >
>



-- 
NS

Re: [VOTE] Git Commit Messages

[Benoit Chesneau <bc...@gmail.com>]

On Thu, Jul 18, 2013 at 8:49 PM, Noah Slater <ns...@apache.org> wrote:

> Well, this is a VOTE thread, so it's not the appropriate place for a
> DISCUSSion. I think the conversation about how we maintain our release
> notes is a very valuable one, and I would like to have that conversation.
>
>
> And the vote has been aborted that's the my point. And I yes I agree we
should start a new discussion thread.

- benoit


> On 18 July 2013 19:41, Benoit Chesneau <bc...@gmail.com> wrote:
>
> > On Thu, Jul 18, 2013 at 8:35 PM, Noah Slater <ns...@apache.org> wrote:
> >
> > > NEWS and CHANGES need to be moved to the docs one way or another, so
> > Dirkan
> > > is doing us a favour by undertaking that effort. If you'd like to
> restart
> > > the discussion as to how we populate our changelog, please start a new
> > > thread.
> > >
> > >
> > Please take the time to read this thread. Also I don't dismiss the work
> > done by djc in any case. I am asking an honest question and you don't
> > answer to it. Also can we continue the discussion on the right thread? Ie
> > the commit one?
> >
> > Thanks.
> >
> > - benoit
> >
>
>
>
> --
> NS
>

Re: [VOTE] Git Commit Messages

[Noah Slater <ns...@apache.org>]

Well, this is a VOTE thread, so it's not the appropriate place for a
DISCUSSion. I think the conversation about how we maintain our release
notes is a very valuable one, and I would like to have that conversation.


On 18 July 2013 19:41, Benoit Chesneau <bc...@gmail.com> wrote:

> On Thu, Jul 18, 2013 at 8:35 PM, Noah Slater <ns...@apache.org> wrote:
>
> > NEWS and CHANGES need to be moved to the docs one way or another, so
> Dirkan
> > is doing us a favour by undertaking that effort. If you'd like to restart
> > the discussion as to how we populate our changelog, please start a new
> > thread.
> >
> >
> Please take the time to read this thread. Also I don't dismiss the work
> done by djc in any case. I am asking an honest question and you don't
> answer to it. Also can we continue the discussion on the right thread? Ie
> the commit one?
>
> Thanks.
>
> - benoit
>



-- 
NS

Re: [VOTE] Git Commit Messages

[Benoit Chesneau <bc...@gmail.com>]

On Thu, Jul 18, 2013 at 8:35 PM, Noah Slater <ns...@apache.org> wrote:

> NEWS and CHANGES need to be moved to the docs one way or another, so Dirkan
> is doing us a favour by undertaking that effort. If you'd like to restart
> the discussion as to how we populate our changelog, please start a new
> thread.
>
>
Please take the time to read this thread. Also I don't dismiss the work
done by djc in any case. I am asking an honest question and you don't
answer to it. Also can we continue the discussion on the right thread? Ie
the commit one?

Thanks.

- benoit

Re: [VOTE] Git Commit Messages

[Noah Slater <ns...@apache.org>]

NEWS and CHANGES need to be moved to the docs one way or another, so Dirkan
is doing us a favour by undertaking that effort. If you'd like to restart
the discussion as to how we populate our changelog, please start a new
thread.


On 18 July 2013 19:12, Benoit Chesneau <bc...@gmail.com> wrote:

> 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
> >
>



-- 
NS

Re: [VOTE] Git Commit Messages

[Benoit Chesneau <bc...@gmail.com>]

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
>

Re: [VOTE] Git Commit Messages

[Noah Slater <ns...@apache.org>]

Benoit, your concerns are orthogonal to the location of the documentation.

Dirkjan, thanks for taking care of this! Long overdue.


On 18 July 2013 13:29, Benoit Chesneau <bc...@gmail.com> wrote:

> On Thu, Jul 18, 2013 at 2:21 PM, Dirkjan Ochtman <di...@ochtman.nl>
> wrote:
>
> > On Mon, May 27, 2013 at 5:42 PM, Robert Newson <rn...@apache.org>
> 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

Re: [VOTE] Git Commit Messages

[Benoit Chesneau <bc...@gmail.com>]

On Thu, Jul 18, 2013 at 2:21 PM, Dirkjan Ochtman <di...@ochtman.nl> wrote:

> On Mon, May 27, 2013 at 5:42 PM, Robert Newson <rn...@apache.org> 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