You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by Brian McCallister <br...@chariotsolutions.com> on 2005/04/06 16:39:04 UTC
Re: JIRA Release Management
+1 for using JIRA for this.
-Brian
On Apr 6, 2005, at 10:41 AM, Martin Kalén wrote:
> JIRA has a number of cool features to make it easy to track in which
> release
> a certain issue got fixed. It can also auto-generate copy/paste
> templates for
> release notes, see eg:
> See eg
> http://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=11111&styleName=Text&projectId=10700&Create=Create
>
> However, this requires that we start specifying explicit release
> numbers instead
> of the 1.0.x/1.x (which seems to work against the purpose of
> release-numbers in JIRA).
>
> If we start using 1.0.3, 1.0.4 etc the release manager can perform a
> project
> release action in JIRA to flush the release notes to start fresh for
> the next
> release.
>
> Any thoughts on this? I think we should start using explicit numbers
> to get
> the most help possible from JIRA.
>
> Regards,
> Martin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org