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

[Hedrick Charles]

I’m going to check in a last-minute feature for Lessons this weekend, and I’d like you to consider adding some support. 

We have an interesting use case that I think may be common. Our largest school is doing increasing fully online work. They asked us to set up a user that could be used by members of their curriculum committee to review courses. Faculty would be asked to add this user as a student.

The problem with this is that if a course uses release control, whether based on date or proper completion of quizzes, a student can’t see all the content without taking the whole course, and possibly without waiting for all the release dates. So I am adding a new permission, lessonbuilder.seeall. I’m going to create a new role and add it to all course sites. I’ll probably call it “reviewer.” You want to consider putting this role in the release. I don’t know whether other tools have the same issue. I’m going to ignore group constraints for that role. It might be useful for other tools to do it as well, though we  could also ask the site owner to add the reviewer to all groups. 



On Dec 6, 2013, at 11:09:12 AM, Matthew Jones <matthew at longsight.com> wrote:

> * I don't know if I'd consider code cleanup (of requiring incorrect dependencies and old code) a blocker for the QA or for the final release, but I don't know if that will be done by next week.
> * We'd just cut at a point in time and put that revision in the externals file, similar to how we cut some of the 2.9 intermediary RC's (like 2.9.2-RC4). [1] I don't think anyone ran those though other than Longsight and just waited for the final release. These, ideally, more places would run.
> 
> We have meetings Monday that will likely generate work. I think realistically the earliest it can be cut is Wednesday, but more likely it would be waiting until after the RM meeting late Thursday or Friday. 
> 
> Cutting it shouldn't be too much work, basically someone
> - Downloads the release at some version
> - Runs this script to create a tag including fixed versions at that revision (https://source.sakaiproject.org/contrib/cle-release/scripts/svnCopyAndFreezeRevision.sh) 
> - Does a build with pack-bin and distributes that to other QA's.
> 
> These initial ones are not going to be real releases. I think we'll want to run the mvn release plugin and see how that goes after we actually cut the branch, but for these first few QA's this will be the procedure.
> 
> [1] https://source.sakaiproject.org/svn/sakai/tags/sakai-2.9.2-rc04/
> 
> 
> 
> On Fri, Dec 6, 2013 at 10:55 AM, Neal Caidin <neal.caidin at apereo.org> wrote:
> 
> 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/d49d2373/attachment.html