[sakai2-tcc] Strawman - Sakai 2.8 Release Activity Scheduling

[Anthony Whyte]

It's an aggressive timeline and a good start but I agree with Steve, it's overly aggressive.  Mid-August Alpha tags I think are unrealistic.  I should note on the subject of dates, that the years are all wrong (2006/2007).

On the issue of ownership, items 3 and 4 are for the TCC to determine, not the PC.  This is clearly stated in the TCC statement of intent and there is no need to be timid on this point.  

"- Determine the scope and schedule for a 2.8 release" 

The PC should be removed as co-owners.  

On tool promotion/deprecation and other goals see:  http://confluence.sakaiproject.org/display/MGT/Sakai+2x+Project+Planning+Goals

As a starting point for debate regarding tool promotion/deprecation: no new capabilities other than CKEditor (if Noah is game); removals: Blogger, reports, warehouse; deprecate: profile (remove 2.9).  None of these recommendations are new; we discussed them in Denver.

Cheers,

Anth


On Jul 21, 2010, at 7:14 PM, Steve Swinsburg wrote:

> We probably need something that outlines feature freeze and code freeze for indie projects? We have quite a few now.
> 
> I think the first few stages of the timeline might be a bit early, like tool promotion and deprecation decisions (they are less than a fortnight away). Do we even have a list of these tools?
> 
> cheers,
> Steve
> 
> On 22/07/2010, at 6:27 AM, May, Megan Marie wrote:
> 
>> Hi everyone,
>>      At the conference there was consensus  that we should release on a time based schedule with a release in early 2011.      I’ve started sketching out the activities that need to occur for a 2.8.0 release by March 1, 2011.     
>>  I’ve been doing this using Excel since it’s easier to manipulate than a table in Confluence.    The current version is attached and it is also out on Confluence at http://confluence.sakaiproject.org//x/8RkhB.
>> What is missing from this list?  Are there items I’ve proposed an insane timeline for?  Are the activity ‘Owners’ correct?  Past schedules have included a kernel freeze although I can’t remember adhering to one – which begs the question, do we really need it?
>> I’ve purposely left some items off the schedule until the general framework (ie code freeze, tags) of schedule is solid or certain people can weigh in:
>> ·         Identify times to touch base with QA Leads (Alan, can you weigh in)
>> o   Accessibility
>> o   Internationalization
>> o   Security
>> o   Performance
>> o    
>> ·         Potential QA Tag Schedule
>> o   Aug 13 - Alpha Tags
>> o   Aug 27
>> o   Sept 10
>> o   Sept 24 - Beta Tags Start
>> o   Oct 8
>> o   Oct 22
>> o   Nov 5
>> o   Nov 19
>> o   Dec 3
>> o   Dec 17
>> o   Dec 31
>> o   Jan 14 - Release Candidate Tags
>> o   Jan 28
>> o   Feb 11
>> o   Feb 25
>> Looking forward to your feedback,  
>> Megan
>>  
>> <Sakai_2-8-0.xls>_______________________________________________
>> sakai2-tcc mailing list
>> sakai2-tcc at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
> 
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20100722/289cd260/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3829 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20100722/289cd260/attachment-0001.bin