tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jianfeng (Jeff) Zhang" <jzh...@hortonworks.com>
Subject Re: Convention for new entries in CHANGES.txt
Date Thu, 04 Dec 2014 01:49:26 GMT
+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 <bikas@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.

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