ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Yang <>
Subject Re: Don't forget the contributor/committer in the CHANGES.txt
Date Sat, 01 Oct 2011 16:27:24 GMT
The format is fine.  Can we take advantage of the Release Note field in jira?  It can automatically
generate both html and text version of CHANGES.txt.  We should have the CHANGES.txt be in
one place instead of man powered CHANGES.txt file.  We only generate CHANGES.txt per release
instead of updating it for every jira.


On Oct 1, 2011, at 8:51 AM, Owen O'Malley wrote:

> All,
>   I think we should follow the Hadoop convention of tagging the
> CHANGES.txt lines with who contributed and committed the patch. I'd
> suggest that it look like:
>  AMBARI-99. Made things better (Joe NonCommitter via omalley)
> and
>  AMBARI-99. Made things better (omalley)
> depending on whether the contributor and committer are the same person.
> Does that make sense?
> -- Owen

View raw message