[WG: Sakai QA] Criteria for changing from a beta release to an RC release during the 2.7 season

[Berg, A.M.]

Hi fellow hard workers,

As Anthony mentioned, I have written a thankfully brief memo over the criteria for changing from one tag type such as beta to another such as release candidate. You can find the 2 page document linked to under http://confluence.sakaiproject.org/display/QA/Short+term+process+improvements

I welcome debate and improvement.

Alan

Alan Berg
Interim QA Director - The Sakai Foundation

Senior Developer / Quality Assurance
Group Education and Research Services
Central Computer Services
University of Amsterdam

http://home.uva.nl/a.m.berg




-----Original Message-----
From: announcements-bounces at collab.sakaiproject.org on behalf of Anthony Whyte
Sent: Tue 1/19/2010 23:20
To: Sakai QA; sakai-dev at collab.sakaiproject.org Developers; announcements at collab.sakaiproject.org
Subject: [Announcements] Draft 2.7.0 release schedule
 
I've added the calendar plugin to the release management space in  
Confluence and laid out a draft release schedule for the upcoming  
Sakai 2.7.0 release (see links below).  The plan is a tentative one  
but assumes the generation of six QA tags (beta/rc) starting on  
Thursday,  21 January, 2009 and released every other Thursday  
thereafter until we judge that sakai-2.7.0 is ready for public release  
(tentative release date: 22 April).  If necessary the schedule  
outlined below will be adjusted should circumstances require it.

For me a critical determinant of whether or not we can keep to the  
schedule below involves transitioning successfully from beta tags to  
release candidates.  Alan Berg has proposed that the transition occur  
only after the following conditions are met:

Beta -> rc transition
1. elimination of all blockers
2. no unassigned critical issues

We should discuss the above criteria (as well as other proposals).  At  
a minimum, I'd like to see a fall in the number of issues lodged  
against successive beta tags before we decide to cut a release  
candidate; however, tracking changes in the defect rate may prove  
challenging.

Tentative schedule (Jan-Feb: beta tags, March-April: rc tags)

21 Jan: sakai-2.7.0-b01
4 Feb: sakai-2.7.0-b02
17 Feb: Properties files string freeze (e.g., i18N)
18 Feb: sakai-2.7.0-b03
4 March sakai-2.7.0-* (beta/rc)
18 March sakai-2.7.0-* (beta/rc)
1 April sakai-2.7.0-* (beta/rc)
15-19 April  sakai-2.7.0 tag/binaries prep
22 April sakai-2.7.0 release

Indie Projects should consider synchronizing their beta/rc candidates  
with the above schedule whenever schedule.

If anyone objects to the draft schedule above please do not hesitate  
to reply to this email.

Cheers,

Anthony

_____________________

Release Management (RM) Space (click "calendar tab or view events panel)
http://confluence.sakaiproject.org/display/REL/Release+Management+Working+Group

RM Calendar
http://confluence.sakaiproject.org/display/REL/Release+Management+Calendar
_______________________________________________
announcements mailing list
announcements at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/announcements

TO UNSUBSCRIBE: send email to announcements-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20100120/9d2efb85/attachment.html