[cle-release-team] 818 issues closed - target a few more?

[Aaron Zeckoski]

Reopened the following for review at the CLE team meeting tomorrow:
https://jira.sakaiproject.org/browse/SAK-22446
https://jira.sakaiproject.org/browse/SAK-20500


Looks like some of those tickets had the 2.9 merge status set by
someone when it should not have been. We might want to consider
restricting who is able to update the merge status fields or at least
make sure we discuss when it is appropriate at the next CLE team call
and then send out a note.

-AZ


On Wed, Aug 22, 2012 at 8:34 AM, Neal Caidin
<nealcaidin at sakaifoundation.org> wrote:
>
> I'm seeing these issues closed in the between Monday and today with :
>
> 2.9.x merge flag set on Closed issue
>
> SAK-22446
> SAK-21775
> SAK-21312
>
>
> 2.8.x merge flag set on Closed issue
>
> SAK-21360
> SAK-21429
> SAK-20500
> SAK-20884
> SAK-19666
>
> 2.7.x merge flag set on Closed Issue
>
> SAK-17162
>
> Should any of these be re-opened? Is there any other Jira indicator we would
> have that an issue should have had a merge?
>
> - Neal
>
> On Aug 21, 2012, at 7:52 PM, Steve Swinsburg <steve.swinsburg at gmail.com>
> wrote:
>
> I presume that these issues require no merges to any maintenance branches?
> Issues shouldn't be closed unless they have had their merges complete, since
> in order to edit the issue after the merge is done to add the new fix
> version, the issue needs to be reopened.
>
> Thanks,
> Steve
>
> Sent from my iPad
>
> On 22/08/2012, at 5:24, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>
> Agreed
> -AZ
>
>
> On Tue, Aug 21, 2012 at 3:21 PM, Sam Ottenhoff <ottenhoff at longsight.com>
> wrote:
>
> Done - Closed.  Safe to say that duplicates are almost always safe to
> close *if* they have a proper link to the correct item set.
>
> --Sam
>
> On Tue, Aug 21, 2012 at 3:18 PM, Neal Caidin
> <nealcaidin at sakaifoundation.org> wrote:
>
> KNL-890
>
> KNL-596
>
> On Aug 21, 2012, at 2:59 PM, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>
> Hit us with the links for convenience :-)
> -AZ
>
>
> On Tue, Aug 21, 2012 at 2:15 PM, Neal Caidin
> <nealcaidin at sakaifoundation.org> wrote:
>
> Okay, there are only two issues left for Kernel and both are labeled as
> duplicate. It would be cool if someone could check into these two issues to
> see if they can be closed.
>
> - Neal
>
> On Aug 21, 2012, at 1:41 PM, Sam Ottenhoff <ottenhoff at longsight.com> wrote:
>
> I don't think you're going to find any of them on this list.... I would feel
> free to proceed with the cleanup.
>
> On Tue, Aug 21, 2012 at 1:30 PM, Neal Caidin
> <nealcaidin at sakaifoundation.org> wrote:
>
>
> FYI, close to 1/2 of these are for SAMIGO.  Could any SAMIGO folks chime
> in and say if it is okay to bulk close these issues?
>
> - Neal
>
>
>
> On Aug 21, 2012, at 12:57 PM, Aaron Zeckoski <aaronz at vt.edu> wrote:
>
> Let's leave KNL out of that list but otherwise this plan looks good to
> me.
> -AZ
>
> On Tue, Aug 21, 2012 at 12:51 PM, Neal Caidin
> <nealcaidin at sakaifoundation.org> wrote:
>
> Done. 818 issues closed (I slightly undercounted the totals the first
> time
> around). I verified that I did not close the Incorporated and
> Incomplete
> issues, the counts for those are the same now as before the bulk close.
>
> I have a new query that could close another 95 issues. Same logic,
> Resolved
> but not Fixed, Incorporated, or Incomplete, but it looks across
> projects -
>
> https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=13573.
> The projects are BLTI, KNL, LSNBLDR, MSND, MSGCNTR, POLL, PRFL , RES,
> SAM,
> SRCH, SHORTURL, STAT.
>
> I cannot see any reason not to close these too? Should I check with any
> listserves outside of CLE?
>
> Thanks,
> Neal
>
>
> 818 issues
> On Aug 20, 2012, at 4:59 PM, Matthew Jones <matthew at longsight.com>
> wrote:
>
> - (Incorporated) That they really were incorporated by some other
> ticket
> (some really aren't and just marked incorrectly)
> - (Incomplete) Why were they incomplete, is there a related ticket for
> completing it?
>
>
>
> _______________________________________________
> 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
>
>
> _______________________________________________
> 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
>
>
> _______________________________________________
> 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
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
>
>
> _______________________________________________
> 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