You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tez.apache.org by Bikas Saha <bi...@hortonworks.com> on 2014/12/02 19:50:56 UTC
Convention for new entries in CHANGES.txt
Folks,
Given that we are now adding all commits to CHANGES.txt, it would help to
have a convention on where to add a new entry. Currently, sometimes its
added to the top and sometimes to the bottom of the changes for a release.
I propose that we follow the convention of adding to the top so that the
latest commit is on top. Choosing the top, since adding new entries (the
most common operation) is quicker this way.
Thanks
Bikas
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Convention for new entries in CHANGES.txt
Posted by Tsuyoshi OZAWA <oz...@gmail.com>.
+1(non-binding), it make sense to me.
On Tue, Dec 2, 2014 at 10:50 AM, Bikas Saha <bi...@hortonworks.com> wrote:
> Folks,
>
>
>
> Given that we are now adding all commits to CHANGES.txt, it would help to
> have a convention on where to add a new entry. Currently, sometimes its
> added to the top and sometimes to the bottom of the changes for a release.
>
>
>
> I propose that we follow the convention of adding to the top so that the
> latest commit is on top. Choosing the top, since adding new entries (the
> most common operation) is quicker this way.
>
>
>
> Thanks
>
> Bikas
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
--
- Tsuyoshi
Re: Convention for new entries in CHANGES.txt
Posted by Mit Desai <mi...@gmail.com>.
+1 for adding entries to top. Would be easier to log the entries that way.
-M!T
On Wed, Dec 3, 2014 at 7:49 PM, Jianfeng (Jeff) Zhang <
jzhang@hortonworks.com> wrote:
> +1 for adding it to the top. If everyone feels OK, I will add this to
> committer guide wiki page
> https://cwiki.apache.org/confluence/display/TEZ/Committer+Guide
>
>
> Best Regards,
> Jeff Zhang
>
>
> On Wed, Dec 3, 2014 at 2:50 AM, Bikas Saha <bi...@hortonworks.com> wrote:
>
> > Folks,
> >
> >
> >
> > Given that we are now adding all commits to CHANGES.txt, it would help to
> > have a convention on where to add a new entry. Currently, sometimes its
> > added to the top and sometimes to the bottom of the changes for a
> release.
> >
> >
> >
> > I propose that we follow the convention of adding to the top so that the
> > latest commit is on top. Choosing the top, since adding new entries (the
> > most common operation) is quicker this way.
> >
> >
> >
> > Thanks
> >
> > Bikas
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
Re: Convention for new entries in CHANGES.txt
Posted by "Jianfeng (Jeff) Zhang" <jz...@hortonworks.com>.
+1 for adding it to the top. If everyone feels OK, I will add this to
committer guide wiki page
https://cwiki.apache.org/confluence/display/TEZ/Committer+Guide
Best Regards,
Jeff Zhang
On Wed, Dec 3, 2014 at 2:50 AM, Bikas Saha <bi...@hortonworks.com> wrote:
> Folks,
>
>
>
> Given that we are now adding all commits to CHANGES.txt, it would help to
> have a convention on where to add a new entry. Currently, sometimes its
> added to the top and sometimes to the bottom of the changes for a release.
>
>
>
> I propose that we follow the convention of adding to the top so that the
> latest commit is on top. Choosing the top, since adding new entries (the
> most common operation) is quicker this way.
>
>
>
> Thanks
>
> Bikas
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.