Benjamin Bentmann wrote:
I'm putting the final touches on the next version of
maven-changes-plugin.
Several enhancements have been made to the JIRA Report. It is now almost
as configurable as a live JIRA "Change Log" view.
Finally I got some time to play around with this. I used something like
<sortColumnNames>Fix Version DESC, Type ASC, Key ASC</sortColumnNames>
and got back a report where the first shown table lines have no "Fix
Version".
That's no issue with the Changes Plugin itself, those issues
(e.g. MJAVACC-1) simply have no version assignments in JIRA. Still, it
looks ugly which leads me to the question, how to fix it.
Are there any reasons why it might be preferable to not specify a fix
version for an issue? Otherwise, I would just assign fix versions
retrospectively (guided by svn logs).
The only time I think it is ok to *not* specify a version, is for issues
that are not tied directly to a release. These are more of tasks, like
"remember to publish the new website" or "announce the release on
freshmeat" and have no bearing on the actual produced artifact. I would
add fix versions retroactively if I were in your shoes.
Benjamin Bentmann
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
