[cle-release-team] Ready for QA server setup

[Neal Caidin]

Looping in Sakai release team.

This is kind of what I was trying to ask on the Sakai Release team call yesterday , but guess I did not articulate it well. Hopefully this will be clearer.

* Do we have any blockers to the release of QA01 (first formal QA testing of Sakai 10) ?
* Is there a preferred revision of trunk we should use? Or is it okay to just cut it at a point in time, and make sure that all QA servers are off the same revision?

I was hoping that we would cut QA01 next week sometime so that we have over a week of testing time available before Christmas week. That assumes someone is available to cut a QA01 tag?

My assumption is that we might need to resolve blockers for feature freeze, but that we want to get started testing in advance of that. 

Thanks,
Neal


Neal Caidin
Sakai Community Coordinator
neal.caidin at apereo.org
Skype: nealkdin
Twitter: ncaidin









On Dec 6, 2013, at 10:10 AM, Neal Caidin <neal.caidin at apereo.org> wrote:

> I was hoping to start QA testing a little earlier than that, maybe next week sometime, so that we have about a 1.5 weeks or so for testing before the week of Christmas. 
> 
> For this round of testing I don’t think we need the blockers fixed?  We will need them fixed before the January Apereo Camp release. 
> 
> 2 cents.
> 
> Neal
> 
> 
> 
> Neal Caidin
> Sakai Community Coordinator
> neal.caidin at apereo.org
> Skype: nealkdin
> Twitter: ncaidin
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Dec 6, 2013, at 10:06 AM, Matthew Jones <matthew at longsight.com> wrote:
> 
>> Whatever date we cut it, that's the release we use. I'd tag it at that version by making a new sakai/tags externals and putting the revision number in there.
>> 
>> There are still two outstanding blockers to remove the gradebook and sections standalone code to make them not depend on impls from edu-services. I started that but it didn't work, I think it could take a half day at least and won't have time till next week. I guess those don't necessarily have to hold up the release since we should still have a meeting to review criticals as well, and there are a lot more patches to merge.
>> 
>> I'd say most likely we'll either just cut it on the 12/13 or 12/20 and go with whatever version it is at the time.
>> 
>> 
>> On Fri, Dec 6, 2013 at 7:56 AM, Neal Caidin <neal.caidin at apereo.org> wrote:
>> Hi all,
>> 
>> We are about ready for QA server setup. Matt and I are going to meet to discuss properties on Monday at noon eastern, 5 pm GMT, which is an open meeting.
>> 
>> How do we decide what revision number of trunk to use for QA? 
>> 
>> Thanks,
>> Neal
>> 
>> 
>> 
>> Neal Caidin
>> Sakai Community Coordinator
>> neal.caidin at apereo.org
>> Skype: nealkdin
>> Twitter: ncaidin
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20131206/1bb1d13e/attachment.html