[WG: Sakai QA] sakai-2.7.0-b02 (next beta tag, Friday, 5 Feb 2010)

[Anthony Whyte]

The next 2.7.0 beta tag is scheduled for this Friday.  Currently,  
there are only 2 closed issues to merge as well as a further 37  
resolved issues with a 2.7.x status of "merge" that have yet to be  
closed.  Many of these resolved issues look to me like they can be  
merged to 2.7.x but I'd prefer that the assignee close the issue as an  
indicator of their readiness for merging.

There is a further backlog of 388 resolved issues that require  
review.  I've spammed the QA list over the last couple of hours with  
requests for specific teams/developers to conduct reviews of resolved  
issues assigned to them so that we can ascertain their current status.

If you working on 2.7.0 issues, please review the two resolved issues  
filter below and if appropriate (e.g., tested/verified or QA is  
planning to test the fix in the next tag) please close resolved issues  
that you own, setting the fix version to sakai-2.7.0-b02 and the 2.7.x  
status to "merge".  If the fix addresses other versions (e.g.,  
sakai-2.6.3) please add this info as well.    And, if you manage your  
own 2.7.x branch please merge when ready.

On Friday, 5 February 2010,  I cut the next beta tag for QA.
_______________________________

2.7.0 closed issues: to merge (n=2)
http://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12212

2.7.0 resolved issues: to merge (n=37)
http://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12213

2.7.0 resolved issues (n=388)
http://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12081

2.7.0 open issues (n=101)
http://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12191

RM calendar
http://confluence.sakaiproject.org/display/REL/Release+Management+Calendar

Cheers,

Anthony