[
https://issues.apache.org/jira/browse/CRUNCH-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560691#comment-13560691
]
Micah Whitacre commented on CRUNCH-63:
--------------------------------------
A good middle ground and something you can have automatically generated would
be to use the maven-changes-plugin[1]. Its a nice way to archive the issues
included in the release in an easily viewable html page. Note it does rely on
Jira summaries and fix versions to be correct for it to provide the most value.
Having the following in the POM:
<issueManagement>
<system>JIRA</system>
<url>http://issues.apache.org/browse/CRUNCH</url>
</issueManagement>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-changes-plugin</artifactId>
<version>2.8</version>
<configuration>
<columnNames>Key,Type,Summary,Assignee,Fix Version</columnNames>
<useJql>true</useJql>
<!--Resolution of Fixed, Complete -->
<resolutionIds>1,12</resolutionIds>
<statusIds>Verified,Closed</statusIds>
<component>${jira.component}</component>
<sortColumnNames>Fix Version DESC, Key DESC</sortColumnNames>
</configuration>
</plugin>
You'd need to change the resolutionIds as those are specific to the JIRA
instance and the property for ${jira.component} would need to be changed to the
appropriate value.
[1] - http://maven.apache.org/plugins/maven-changes-plugin/
> Add a CHANGES.txt
> -----------------
>
> Key: CRUNCH-63
> URL: https://issues.apache.org/jira/browse/CRUNCH-63
> Project: Crunch
> Issue Type: Task
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
>
> It will be useful to have a CHANGES.txt to clearly communicate new-features,
> incompatible changes, bug-fixes etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
