Re: Commits should include CHANGES.txt update

2014-08-05 Thread Kevin Minder

This makes sense to me and isn't too much overhead.

On 8/5/14 4:30 PM, larry mccay wrote:

Folks -

I feel as though we should uptake the policy that is used for Hadoop common
commits where every commit includes a record of the change in CHANGES.txt.

This will make the release process easier since we won't have to backfill
all of the changes at release candidate creation time.

Also, as we take on more of the policies and procedures of the rest of
Hadoop it will make us better committers on other projects when that is
appropriate.

thoughts?

thanks,

--larry




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


Commits should include CHANGES.txt update

2014-08-05 Thread larry mccay
Folks -

I feel as though we should uptake the policy that is used for Hadoop common
commits where every commit includes a record of the change in CHANGES.txt.

This will make the release process easier since we won't have to backfill
all of the changes at release candidate creation time.

Also, as we take on more of the policies and procedures of the rest of
Hadoop it will make us better committers on other projects when that is
appropriate.

thoughts?

thanks,

--larry