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

Wed Aug 22 16:01:59 PDT 2012

I think we need to rationalise these pages, there is just too much information, and a lot of the info is duplicated.

When I did the 2.8.2 release I updated these pages:
https://confluence.sakaiproject.org/display/DOC/Sakai+CLE+2.8+release+notes

But even still there are a list of Jira tickets that had been manually added to the page that were apparently fixed for some 2.8 release which were no longer applicable. IMO that should just be a link to a filter as its out of date as soon as its entered. Plus we have a stack of indies that have their own release schedule so its difficult to collate them all.

It would be good for a 2.8.2 (and 2.9.0) version of this page to be created so we have a record for the release:
https://confluence.sakaiproject.org/display/REL/sakai-2.8.1

but at the same time have the 'release notes' page trimmed.

cheers,
Steve

On 23/08/2012, at 7:33 AM, Neal Caidin <nealcaidin at sakaifoundation.org> wrote:

> Yep, that's what I was hoping for.  Right now the sakai-2.9.0-b03  points to a blank page, whereas  sakai-2.8.1 points to a nice summary of the 2.8.1 configuration (I guess nobody got around to updating for 2.8.2).
> 
> -- Neal
> 
> 
> 
> On Aug 22, 2012, at 5:24 PM, Matthew Jones <matthew at longsight.com> wrote:
> 
>> Probably adding a 2.9.0 page there sometime in the next few weeks that's similar to the old 2.8 pages?
>> 
>> On Wed, Aug 22, 2012 at 5:16 PM, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>> I don't see any dates on that page. What do you mean?
>> -AZ
>> 
>> 
>> On Wed, Aug 22, 2012 at 5:09 PM, Neal Caidin
>> <nealcaidin at sakaifoundation.org> wrote:
>> > Speaking of which … could somebody please update
>> > https://confluence.sakaiproject.org/display/REL/Releases for the 2.9.x
>> > release-to-date?  If it is not too much trouble.
>> >
>> > Might help with some of this ticket sleuthing.
>> >
>> > Thanks,
>> > Neal
>> >
>> >
>> > On Aug 22, 2012, at 5:01 PM, Steve Swinsburg <steve.swinsburg at gmail.com>
>> > wrote:
>> >
>> > There are probably more since the cross project filter would not have picked
>> > up the other various merge status flags (i.e. Profile2 has 1.4.x and 1.5.x
>> > for its branches since its an indie).
>> >
>> > cheers,
>> > S
>> >
>> >
>> > On 22/08/2012, at 10:34 PM, 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
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20120823/95dbf075/attachment-0006.html 