[WG: Sakai QA] Release Management Call, Thursday 1 July 2010, 10 AM EDT

Anthony Whyte arwhyte at umich.edu
Wed Jun 30 12:06:55 PDT 2010


Let's regroup and discuss 2.6.3 as well as a proposal Charles made during the Denver conference regarding future release practices:

Hedrick: "For 2.8 I'd like to propose that if anyone wants to declare a problem that exists in 2.7 a blocker for 2.8, they have to do it by January 1. While I'd like to see many of them get fixed (and I'm willing to help do so), I'd like not to hold a release for existing problems. It would be great to have a completely bug-free release. But that's unlikely. When we have a release that's unambiguously in better shape than the last one, it shouldn't get derailed because it hasn't fixed every bug. Given academic schedules, being delayed significantly means that many sites can't consider it for the Fall."

A second proposal discussed at the Conference involved creating a list to be used to broadcast release information.

cheers,

Anthony


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/20100630/9948d8db/attachment.html 


More information about the sakai-qa mailing list