crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Micah Whitacre (JIRA)" <>
Subject [jira] [Commented] (CRUNCH-63) Add a CHANGES.txt
Date Wed, 23 Jan 2013 14:00:14 GMT


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:


	     <columnNames>Key,Type,Summary,Assignee,Fix Version</columnNames>
             <!--Resolution of Fixed, Complete -->
	     <sortColumnNames>Fix Version DESC, Key DESC</sortColumnNames>

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] -
> Add a CHANGES.txt
> -----------------
>                 Key: CRUNCH-63
>                 URL:
>             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:

View raw message