You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by Flavio Junqueira <fp...@apache.org> on 2016/12/16 11:14:05 UTC
CHANGES.txt?
Could anyone remind me of what we decided for CHANGES.txt? Are we supposed to add resolved jiras to it or are we going to rely on the git log?
I have committed ZK-761 to master without the change to CHANGES.txt, but then I noticed that some commits are going in with it, so I did it to the 3.5 branch. I want to know if I need to make it consistent or not.
-Flavio
Re: CHANGES.txt?
Posted by Rakesh Radhakrishnan <ra...@apache.org>.
Hi All,
I hope all are agreeing to remove CHANGE.txt file from ZK project
repository. I believe, ZOOKEEPER-2672 jira needs to be concluded(to avoid
confusions) before cutting 3.4.10 release. I'm planning to remove
CHANGE.txt file in 2 days time frame, 8 February 2017, 6:00 PM (PST), if
there is no objection. Thanks!
Thanks & Regards,
Rakesh
On Thu, Feb 2, 2017 at 9:06 PM, Rakesh Radhakrishnan <ra...@apache.org>
wrote:
> +1 for removing the CHANGE.txt file.
>
> I agree to rely on source control (github) revision logs instead of
> CHANGE.txt moving forward.
>
> Note: Jira issue ZOOKEEPER-2672 will be used to remove this file.
>
> Thanks,
> Rakesh
>
>
> On Sat, Dec 17, 2016 at 3:59 AM, Michael Han <ha...@cloudera.com> wrote:
>
>> See https://www.mail-archive.com/dev@zookeeper.apache.org/msg37108.html
>>
>> I think there was no decision explicitly made but looks like every one was
>> OK to head towards the direction of removing CHANGE.TXT.
>>
>> On Fri, Dec 16, 2016 at 3:14 AM, Flavio Junqueira <fp...@apache.org> wrote:
>>
>> > Could anyone remind me of what we decided for CHANGES.txt? Are we
>> supposed
>> > to add resolved jiras to it or are we going to rely on the git log?
>> >
>> > I have committed ZK-761 to master without the change to CHANGES.txt, but
>> > then I noticed that some commits are going in with it, so I did it to
>> the
>> > 3.5 branch. I want to know if I need to make it consistent or not.
>> >
>> > -Flavio
>>
>>
>>
>>
>> --
>> Cheers
>> Michael.
>>
>
>
Re: CHANGES.txt?
Posted by Rakesh Radhakrishnan <ra...@apache.org>.
Hi All,
I hope all are agreeing to remove CHANGE.txt file from ZK project
repository. I believe, ZOOKEEPER-2672 jira needs to be concluded(to avoid
confusions) before cutting 3.4.10 release. I'm planning to remove
CHANGE.txt file in 2 days time frame, 8 February 2017, 6:00 PM (PST), if
there is no objection. Thanks!
Thanks & Regards,
Rakesh
On Thu, Feb 2, 2017 at 9:06 PM, Rakesh Radhakrishnan <ra...@apache.org>
wrote:
> +1 for removing the CHANGE.txt file.
>
> I agree to rely on source control (github) revision logs instead of
> CHANGE.txt moving forward.
>
> Note: Jira issue ZOOKEEPER-2672 will be used to remove this file.
>
> Thanks,
> Rakesh
>
>
> On Sat, Dec 17, 2016 at 3:59 AM, Michael Han <ha...@cloudera.com> wrote:
>
>> See https://www.mail-archive.com/dev@zookeeper.apache.org/msg37108.html
>>
>> I think there was no decision explicitly made but looks like every one was
>> OK to head towards the direction of removing CHANGE.TXT.
>>
>> On Fri, Dec 16, 2016 at 3:14 AM, Flavio Junqueira <fp...@apache.org> wrote:
>>
>> > Could anyone remind me of what we decided for CHANGES.txt? Are we
>> supposed
>> > to add resolved jiras to it or are we going to rely on the git log?
>> >
>> > I have committed ZK-761 to master without the change to CHANGES.txt, but
>> > then I noticed that some commits are going in with it, so I did it to
>> the
>> > 3.5 branch. I want to know if I need to make it consistent or not.
>> >
>> > -Flavio
>>
>>
>>
>>
>> --
>> Cheers
>> Michael.
>>
>
>
Re: CHANGES.txt?
Posted by Rakesh Radhakrishnan <ra...@apache.org>.
+1 for removing the CHANGE.txt file.
I agree to rely on source control (github) revision logs instead of
CHANGE.txt moving forward.
Note: Jira issue ZOOKEEPER-2672 will be used to remove this file.
Thanks,
Rakesh
On Sat, Dec 17, 2016 at 3:59 AM, Michael Han <ha...@cloudera.com> wrote:
> See https://www.mail-archive.com/dev@zookeeper.apache.org/msg37108.html
>
> I think there was no decision explicitly made but looks like every one was
> OK to head towards the direction of removing CHANGE.TXT.
>
> On Fri, Dec 16, 2016 at 3:14 AM, Flavio Junqueira <fp...@apache.org> wrote:
>
> > Could anyone remind me of what we decided for CHANGES.txt? Are we
> supposed
> > to add resolved jiras to it or are we going to rely on the git log?
> >
> > I have committed ZK-761 to master without the change to CHANGES.txt, but
> > then I noticed that some commits are going in with it, so I did it to the
> > 3.5 branch. I want to know if I need to make it consistent or not.
> >
> > -Flavio
>
>
>
>
> --
> Cheers
> Michael.
>
Re: CHANGES.txt?
Posted by Rakesh Radhakrishnan <ra...@apache.org>.
+1 for removing the CHANGE.txt file.
I agree to rely on source control (github) revision logs instead of
CHANGE.txt moving forward.
Note: Jira issue ZOOKEEPER-2672 will be used to remove this file.
Thanks,
Rakesh
On Sat, Dec 17, 2016 at 3:59 AM, Michael Han <ha...@cloudera.com> wrote:
> See https://www.mail-archive.com/dev@zookeeper.apache.org/msg37108.html
>
> I think there was no decision explicitly made but looks like every one was
> OK to head towards the direction of removing CHANGE.TXT.
>
> On Fri, Dec 16, 2016 at 3:14 AM, Flavio Junqueira <fp...@apache.org> wrote:
>
> > Could anyone remind me of what we decided for CHANGES.txt? Are we
> supposed
> > to add resolved jiras to it or are we going to rely on the git log?
> >
> > I have committed ZK-761 to master without the change to CHANGES.txt, but
> > then I noticed that some commits are going in with it, so I did it to the
> > 3.5 branch. I want to know if I need to make it consistent or not.
> >
> > -Flavio
>
>
>
>
> --
> Cheers
> Michael.
>
Re: CHANGES.txt?
Posted by Michael Han <ha...@cloudera.com>.
See https://www.mail-archive.com/dev@zookeeper.apache.org/msg37108.html
I think there was no decision explicitly made but looks like every one was
OK to head towards the direction of removing CHANGE.TXT.
On Fri, Dec 16, 2016 at 3:14 AM, Flavio Junqueira <fp...@apache.org> wrote:
> Could anyone remind me of what we decided for CHANGES.txt? Are we supposed
> to add resolved jiras to it or are we going to rely on the git log?
>
> I have committed ZK-761 to master without the change to CHANGES.txt, but
> then I noticed that some commits are going in with it, so I did it to the
> 3.5 branch. I want to know if I need to make it consistent or not.
>
> -Flavio
--
Cheers
Michael.