On Dec 16, 2008, at 5:46 AM, Jukka Zitting wrote:
Hi,
On Mon, Dec 15, 2008 at 8:26 PM, Mattmann, Chris A
<[email protected]> wrote:
+1, I agree with Grant's comment. I also like the simplicity of
having a
text file, separate of JIRA. What I find quite often (we use JIRA
at work,
and deploy our open source software on various projects) is that
folks don't
know what JIRA is, or care, but they like having a text file that
comes
along with the release that they can refer to, and at least get a
high level
view of what's going on in terms of updates and features for a
release.
Agreed on the importance of having high level release notes in
writing. However, I don't think that the current CHANGES.txt format of
just listing the resolved issues is any better than the report from
Jira.
Sure, JIRA can generate that file for you, using the release notes,
but like
Grant said, it takes out the (some guy X via some committer Y), or
(some
committer Y) comments, which are nice to give folks credit.
Jira also has a pretty good contribution report (see [1] for the 0.2
release) where you can see all the people who've contributed to a
release.
Very cool. I didn't know that. I agree that manually maintaining it
is a pain in the butt. Perhaps it would be reasonable to generate a
PDF from it for inclusion in a release, that way there is a more
permanent record of it included. In fact, that report is looks better
than the current way, which is usually left to the committer.
[1]
https://issues.apache.org/jira/secure/ConfigureReport.jspa?versionId=12312902&selectedProjectId=12310631&reportKey=com.sourcelabs.jira.plugin.report.contributions%3Acontributionreport&Next=Next
-Grant
