Mailing List Archive

[jira] [Commented] (FOR-853) Links: using Jira to manage issues for next release
[ https://issues.apache.org/jira/browse/FOR-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566201#comment-16566201 ]

David Crossley commented on FOR-853:
------------------------------------

This is an old issue (but never finalised). The document http://forrest.apache.org/procedures/release/How_to_release.html will be the most useful at this stage.

> Links: using Jira to manage issues for next release
> ---------------------------------------------------
>
> Key: FOR-853
> URL: https://issues.apache.org/jira/browse/FOR-853
> Project: Forrest
> Issue Type: Bug
> Components: Discussion links to archives, Project administration
> Reporter: David Crossley
> Priority: Major
>
> We have an incomplete discussion about how to use Jira to assist with management of our issues, and a classification method to identify issues for the next release, and Jira filters so that we can see important outstanding issues at a glance. This needs to be finalised and documented (probably in /issues.html)
> and also need to document our procedure for release.
> Re: planning the 0.8 release (Was: [RT] structurer location and resource types)
> http://marc.theaimsgroup.com/?t=114324667300003



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FOR-853) Links: using Jira to manage issues for next release [ In reply to ]
[ https://issues.apache.org/jira/browse/FOR-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569140#comment-16569140 ]

Gavin commented on FOR-853:
---------------------------

Sure, I think what I did to bump this issue was update some of the mail thread links.

Whilst Im here , my take on this is

a) Drop use of the Urgency Field, it isnt needed
b) Add in use of the 'Target Version/s field.

expanding on b) , Using Target Version/s field ensures that we use 'Fix Version' only once something has been closed as Fixed and put into a release. Otherwise Fix Version stays blank and Target Version/s gets used for 'what we think' .

This freeing up of 'Fix Version' allows better use of the 'Release Notes' facility in Jira also.

Happy to defer decision making on this until after the current 0.10 gets out the door.

> Links: using Jira to manage issues for next release
> ---------------------------------------------------
>
> Key: FOR-853
> URL: https://issues.apache.org/jira/browse/FOR-853
> Project: Forrest
> Issue Type: Bug
> Components: Discussion links to archives, Project administration
> Reporter: David Crossley
> Priority: Major
>
> We have an incomplete discussion about how to use Jira to assist with management of our issues, and a classification method to identify issues for the next release, and Jira filters so that we can see important outstanding issues at a glance. This needs to be finalised and documented (probably in /issues.html)
> and also need to document our procedure for release.
> Re: planning the 0.8 release (Was: [RT] structurer location and resource types)
> http://marc.info/?t=114324667300003



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)