[WG: Sakai QA] CLE Release / Maintenance Team call, Thur 1 Sept 2011, 10 AM EDT

Anthony Whyte arwhyte at umich.edu
Wed Aug 31 23:21:50 PDT 2011


Both sakai-2.7.2 and sakai-2.8.1 have been wrestling with a number of issues that have delayed their release.  In particular, there are a number of tickets that we need to review relative to progress and I also suggest that we discuss our current practices relative to bug handling/local testing/branch management/jira ticket workflow as I think a review is in order.

Cheers,

Anthony

Regressions / Blockers
Announcements: https://jira.sakaiproject.org/browse/SAK-21071 / https://jira.sakaiproject.org/browse/SAK-18641
Samigo: https://jira.sakaiproject.org/browse/SAM-1286
Samigo: https://jira.sakaiproject.org/browse/SAM-1244
Kernel: https://jira.sakaiproject.org/browse/KNL-796

Discussion: is KNL-796 truly a blocker?  I ask this with respect to 2.7.2 as kernel-1.1.13 was cut earlier (the 2.7.2 release branch is running off it; I have yet to update 2.7.x).  This is a fix to kernel-util and if this regression is regarded as a blocker one we will have to re-release all 2.7-related indies since kernel-util is bundled up in their webapp.  The same would be true of 2.8.1.

CLE open blockers
https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12708


CONNECTION INFO

Telephone: +1 812 856 7060
Polycom or Lifesize: 156.56.240.100##22X
Tandberg or XMeeting: 22X at 156.56.240.100
GDS E.164: 0011439X

Conference Code: 22348#
PIN: 72524



Begin forwarded message:

> From: Anthony Whyte <arwhyte at umich.edu>
> Date: August 17, 2011 5:34:36 PM GMT+01:00
> To: Developers Sakai-Dev <sakai-dev at collab.sakaiproject.org>, Sakai QA <sakai-qa at collab.sakaiproject.org>
> Subject: CLE Release / Maintenance Team call, Thur 18 Aug 2011, 10 AM EDT
> 
> Both sakai-2.7.2 and sakai-2.8.1 are hung up at the moment awaiting resolution of blockers or tire kicking by QA.  We need to discuss how best to get these releases out the door so that we can refocus efforts on sakai-2.9.
> 
> 2.7.2 STATUS
> 
> UCT is running sakai-2.7.x, r96207 in production.  The sakai-2.7.2 release branch was created from 2.7.x, starting at r96049, 2 Aug 2011.  Since then there have been 16 commits to 2.7.x, including 6 help updates.  All have been merged to the 2.7.2 release branch (the help commits automatically) as of r97032.    
> 
> After a shaky start Stephen Marquard reported as of 12 August 2011: 
> 
> "we are back to the usual background level of bugs. The only one that may be new that I don't think we've yet got to the bottom of is the Announcements/Assignments bug."  See UCT bug summary: https://vula.uct.ac.za/mrtg/bug-summary.html.
> 
> The bug Stephen refers to is:  https://jira.sakaiproject.org/browse/SAK-21036  (copy of https://jira.cet.uct.ac.za/browse/VULA-1384)
> 
> MySQL/Oracle conversion scripts also need to be retested due to https://jira.sakaiproject.org/browse/SAK-20598.  I'm re-testing the MySQL scripts this afternoon.
> 
> 2.7.x resolved/closed (to merge)
> https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12212
> 
> I don't plan on merging any of these ticket fixes for 2.7.2.  Most generate merge conflicts.  One possible exception is
> 
> https://jira.sakaiproject.org/browse/SAK-20980
> 
> We are also still running off of kernel-1.1.13-SNAPSHOT.  A late-breaking NPE may be worth fixing before the release although it looks like its  not a core path issue but flairs up when you remove a property from a DB user:
> 
> https://jira.sakaiproject.org/browse/KNL-789
> 
> .
> 2.8.1 STATUS
> 
> The 2.8.1 release branch was created from 2.8.x, starting at r96298 on 3 Aug 2011.  Since then all 2.8.x commits have been merged to 2.8.1 as or r97134 except for the following:
> 
> https://jira.sakaiproject.org/browse/SAK-20798  (fix version=2.8.2)
> https://jira.sakaiproject.org/browse/SAK-21004 (fix version=2.8.2)
> 
> Late-breaking regressions have hampered 2.8.1 release efforts as has trying to find a server admin available to install a running instance of the 2.8.1 release branch on a QA server (got this done yesterday) to support a QA test fest.
> 
> https://jira.sakaiproject.org/browse/SAK-20996 StringUtil.swap() -> commons StringUtils.swap() causes regressions (rwiki -- fixed, merged)
> https://jira.sakaiproject.org/browse/SAK-21026 StringUtil.swap() -> commons StringUtils.swap() causes regressions (citations, email archive -- may still require testing before merging)
> 
> MySQL/Oracle conversion scripts also need to be retested due to https://jira.sakaiproject.org/browse/SAK-20598.   I'm re-testing the MySQL scripts this afternoon.
> 
> 2.8.x resolved/closed (to merge)
> https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12536
> 
> Again, I doubt Sam or I will merge any of these fixes except SAK-21026 and perhaps SAK-21019, SAK-20980, SAK-20957, SAK-20962, SAK-19041 (accessibility), SAK-15826.  The latter all need to be assessed tomorrow.
> 
> Later,
> 
> Anth
> 
> _______________________
> 
> 
> CLE open blockers
> https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12708
> 
> 
> CONNECTION INFO
> 
> Telephone: +1 812 856 7060
> Polycom or Lifesize: 156.56.240.100##22X
> Tandberg or XMeeting: 22X at 156.56.240.100
> GDS E.164: 0011439X
> 
> Conference Code: 22348#
> PIN: 72524
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20110901/49e90cd5/attachment.html 


More information about the sakai-qa mailing list