[WG: Sakai QA] [cle-release-team] Status of 2.9.1-rc01 and next steps

Anthony Whyte arwhyte at umich.edu
Fri Jan 25 12:58:25 PST 2013


> Then a recommendation from CLE release team to take back to TCC. (Not sure of TCC process on dot releases, but I guess we'll find out!).


The process is very light-weight.  This is what you do:

When, in the opinion of the release team--after consulting with the Security, QA and Accessibility WGs--the final release tag and accompanying artifacts are ready to be generated, the release lead should send an email to the TCC stating that the release is ready and request that the chair schedule a vote on release readiness.  Turn around on the vote should be quick unless objections are raised.

In between now and then ping the TCC, Dev and QA lists with 2.9.1 status updates, especially whenever a late-breaking blocker threatens the schedule (like you did earlier this morning).

Reviewing the history of the last 5 release events, formal votes have only been recorded for three releases [1].  A case might be made for adopting a lazy consensus approach, with the release team pinging the TCC and declaring its intention to release 2.9.1 on X date barring substantive objections.  But you should check with the TCC chair, Megan May.  Scheduling a vote is no big deal and puts each TCC member on record as regards their view of 2.9.1 release readiness.

Cheers,

Anth

[1] TCC era release approval:
2.9.0: vote, http://collab.sakaiproject.org/pipermail/sakai2-tcc/2012-November/002434.html
2.8.2: no vote recorded, however, release readiness may have been discussed at a F2F TCC meeting, 10 June 2012; draft release announcement discussed by TCC http://collab.sakaiproject.org/pipermail/sakai2-tcc/2012-June/002078.html
2.8.1: no vote, Sam and I cranked this one out during Oct 2011 after I had joined OAE but before anyone else had taken over release duties.  Both the release team and TCC members wanted this release cut.
2.8.0: vote, http://collab.sakaiproject.org/pipermail/sakai2-tcc/2011-April/001060.html
2.6.3/2.7.1: vote, http://collab.sakaiproject.org/pipermail/sakai2-tcc/2010-August/000159.html


Cheers,

Anth



On Jan 25, 2013, at 2:17 PM, Neal Caidin wrote:

> Hi All,
> 
> [I'm looking for feedback, especially from active testers and developers.]
> 
> Sorry for long email. 
> 
> Status
> --------------
> We've had good coverage of shallow regression testing. Little or no testing on merged Jiras, but we had already had most of these Jiras verified in trunk and then again in 2.9.x in the pre-RC01 testing. 
> 
> Three bugs were reported in this round of RC01 testing. Two were blockers and one is a regression against 2.9.0, but I don't think it is a blocker. 
> 
> https://jira.sakaiproject.org/browse/SAK-23161 -IE9: Portal page not displaying properly, unable to view sites after log in - Blocker / Fixed and merged into 2.9.x
> https://jira.sakaiproject.org/browse/MSGCNTR-772 - Moderate Message  - Approve button click generates an error - Blocker / Fixed and merged into 2.9.x  (3.0.x is MSGCNTR equivalent)
> 
> https://jira.sakaiproject.org/browse/SAK-23165 - Help (?) content for calendar and my workspace info display tools does not display any help content - this is a regression against 2.9.0, but I don't think it should be a blocker - If somebody wants to put about 30 minutes into reverting this back to the old text, it could be fixed. I'll check with Documentation team to see if this was intentional.
> 
> Proposal
> -------------------
> I'm thinking we should test the fixes, SAK-23161 and MSGCNTR-772 on the nightly 2.9.x server by Monday and if they pass, proceed with the 2.9.1 GA (general availability, aka production) next week. 
> 
> 
> Alternative
> ------------------------------
> The alternative, which wouldn't be too bad, is to have an RC02 test fest. This would delay the release by a week or more, probably closer to a week and a half to two weeks, since there will be nobody in the QA coordination role (I'm out next week, returning a week from Tuesday).  We could possibly get RC02 built by tonight. 
> 
> Looking for feedback initially on the proposal. Then a recommendation from CLE release team to take back to TCC. (Not sure of TCC process on dot releases, but I guess we'll find out!).
> 
> Cheers,
> 
> Neal Caidin
> 
> Sakai CLE Community Coordinator
> nealcaidin at sakaifoundation.org
> Skype: nealkdin
> AIM: ncaidin at aol.com
> 
> 
> 
> _______________________________________________
> 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/sakai-qa/attachments/20130125/d032910f/attachment.html 


More information about the sakai-qa mailing list