Should we consider the maven groupId change separately from the package
name change?
On 8/5/14 1:58 PM, larry mccay wrote:
Yes - that is a good point and should be done regardless of version
designation but certainly if we are to go with a 1.0.
On Tue, Aug 5, 2014 at 12:37 PM, Kevin Minder
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,
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