[sakai2-tcc] [Building Sakai] [Management] Sakai 2.8 Release Activity Schedule

[Berg, Alan]

Hi,

Firstly i recognise that the TCC is responsible for shepherding  2.X  and Hybrid mode is instigated in the Sakai 3 project structure, however qua technology it has feet in both 2 and 3. . I think you read the situation correctly qua impact for 2.8, the functionality is turned off by default.  Qua impact for central  testing resources we have to look at the wider picture of the timeline of the hybrid mode and bug fixing in three places Saka 2.x, Sakai 3 and directly by Lance with the gluing. I discussed this with Lance yesterday and promised to send an email to the TCC and Alan Marks, but you beat me to the punch. 

There are two versions of hybrid promised Basic and Complete. The complete version has not been documented qua functionality but needs to be ready at the end of Q2 of the Sakai 3 project plan by June 2011.

The rough timeline for testing should look similar to: Sakai 2.8 goes from alpha to beta. Hybrid mode is tested against the beta and  bugs are pushed back to Sakai 2.x and Sakai 3 and the responsible party for the glue. The cycle is kept in check with the 2 week tagging cycle of the beta's. Testing needs to include functional testing, security, UI consistency, performance. Central QA needs to know what the landing time for the complete mode and actuate the cycle again. The testing resources need to be found from the community. I would expect those testers to come for the Sakai 3 project, but that is not clear as we have a general lack of resources. The bug fixes for at least the basic mode will need to be in step with the release of 2.8. Bug fixes associated with UI consistency may need to be negotiated as they have no immediate value for 2..8 or Sakai 3. The impact for Lance is that he will need good test plans for the full hybrid functionality and no doubt he will need to be quick with his programming fingers.

Alan

Alan Berg
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

________________________________________
From: sakai2-tcc-bounces at collab.sakaiproject.org [sakai2-tcc-bounces at collab.sakaiproject.org] on behalf of csev [csev at umich.edu]
Sent: 02 September 2010 05:06
To: Lance Speelmon; Sakai 2 Technical Coordination Committee
Subject: Re: [sakai2-tcc] [Building Sakai] [Management] Sakai 2.8 Release       Activity Schedule

Just to shorten this to get a little more detail, I cut down the discussion breadth.

I took a *really quick* look at this at a high level and it seems like most of it would ship as turned off out of the box in 2.8 but with code in place and ready to be activated with a property.

If that is the case, then in my opinion, this is an easy one to say yes to - all we need is a simple 2.8 test plan to test to make sure that all this stuff is disabled out of the box - and then later, it can emerge as needed , perhaps with a few tweaks in the 2-8-x branch if needed.

In a sense, if I am reading it correctly, this is like IMS BLTI Provider was in 2.7.0 - there and maybe useful - but turned off out of the box.

Do the KERN JIRAs need to be landed, or is that somewhat independent from a 2.8 perspective?

Or did I miss something?

/Chuck

On Sep 1, 2010, at 1:01 PM, Speelmon, Lance Day wrote:

> Seth,
>
> I have added my proposal to the page as a comment.  Thanks, L
>
>
> Lance Speelmon
> Scholarly Technologist
_______________________________________________
sakai2-tcc mailing list
sakai2-tcc at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc