[cle-release-team] [Jira process] When to close an issue
Steve Swinsburg
steve.swinsburg at gmail.com
Tue Jun 25 05:42:39 PDT 2013
FYI there was a discussion about this in Nov/Dec 2012, titled 'JIRA Version Maintenance'. It's mixed in with that.
On 25/06/2013, at 10:35 PM, Neal Caidin <neal.caidin at apereo.org> wrote:
> Something that I didn't consider when closing issues is that while the issue may be fixed, verified and merged into 2.9.x , maybe it should not be closed until the 2.8.x merge is complete as well (assuming that there is a 2.8.x merge flag set) ?
>
> Steve Swinsburg brought this to my attention on one issue.
>
> I just ran a query and notice 28 issues which are closed but the 2.8.x merge flag is set and not yet resolved. I'm guessing this mostly happens when I do those "bulk closes", because then I don't see those nuances.
>
> Here is the query to capture current closed issues with unresolved 2.8.x merge flag - status = Closed and "2.8.x Status" = merge
>
> What do you think?
>
> Thanks,
>
> Neal Caidin
> CLE Community Coordinator
> neal.caidin at apereo.org
> Skype: nealkdin
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20130625/367a6f0d/attachment.html
More information about the cle-release-team
mailing list