[cle-release-team] [Jira process] When to close an issue

[Neal Caidin]

Okay. I'll explore what it takes to modify my queries when I work on bulk
closes.

To keep things simple administratively, I do not plan to re-open those 28
issues. Is that okay?

At least we have a query to identify them easily.

- Neal



On Tue, Jun 25, 2013 at 8:42 AM, Aaron Zeckoski <azeckoski at unicon.net>wrote:

> That's correct. Issues should not be closed unless they are verified
> and merge flags are set to a resolution (none, won't, resolved).
> -AZ
>
>
> On Tue, Jun 25, 2013 at 8:35 AM, 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
> >
>
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20130625/407b1d33/attachment.html