[sakai2-tcc] Sakai 2.10 schedule - strawperson

classic Classic list List threaded Threaded
3 messages Options
Neal Caidin-3 Neal Caidin-3
Reply | Threaded
Open this post in threaded view
|

[sakai2-tcc] Sakai 2.10 schedule - strawperson

[ CLE release team and PMC (formerly known as TCC)]

We need to come up with a schedule for 2.10.  

Strawperson [for discussion] - High level milestone targets

-------------------------------------------------
2013 mid-Oct  - Scope Freeze
2013 late-Nov  - Branch cut - Alpha 01
2014 early-March - Beta 01
2014 early-May - RC01
2014 mid-July - GA (General Availability aka production)


This seems to me like a realistic schedule, based on looking at the actual schedules for 2.8 and 2.9 (and taking into account losing your coordinator during 2.9) and that during November, December and January, I don't think we will have much QA resources available. Also, we will have the Apereo Conference in June 2014, which might slow things down a tad. If I try working backwards from a May 15 date for a release, it just doesn't add up. 

The discussion will be for the CLE release team meeting tomorrow. 

Thanks!
Neal


Neal Caidin
Sakai CLE Community Coordinator
Skype: nealkdin
Twitter: ncaidin










_______________________________________________
sakai2-tcc mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
Matthew Jones-2 Matthew Jones-2
Reply | Threaded
Open this post in threaded view
|

Re: [sakai2-tcc] [cle-release-team] Sakai 2.10 schedule - strawperson

I think this sounds good, but I'm a little more optimistic about the dates.

We're planning on a feature identification freeze this week. This includes all features that have patches attached which are desired for 2.10. Some of these will require manual conflict resolution to update from older patch code so will take awhile. The actual feature merge work should be done by the end of October which would be the true feature freeze. Then after all outstanding blockers are resolved we can cut the branch and the first alpha by mid-late November. It should be done prior to Thanksgiving as has been stated in the past, so by Friday November 22.

I don't think we'll be on Alphas all the way until March. The Alpha process is mostly waiting for translation to complete and resolving issues found in QA so it could be variable but I don't anticipate any seriously time consuming issues. With the unconference at the end of January, I'd put Beta 01 in early February rather than early March, with the presumption that at least a few people who can work on the release will be present and working to finish out whatever is needed for Beta at the unconference. That could bump the other dates up by a month which would be ideal, given the date of the Juneconference, and the 6 month release schedule of the 2.8 release which was a more typical schedule than 2.9.

On Wed, Oct 2, 2013 at 10:31 AM, Neal Caidin <[hidden email]> wrote:
[ CLE release team and PMC (formerly known as TCC)]

We need to come up with a schedule for 2.10.  

Strawperson [for discussion] - High level milestone targets

-------------------------------------------------
2013 mid-Oct  - Scope Freeze
2013 late-Nov  - Branch cut - Alpha 01
2014 early-March - Beta 01
2014 early-May - RC01
2014 mid-July - GA (General Availability aka production)


This seems to me like a realistic schedule, based on looking at the actual schedules for 2.8 and 2.9 (and taking into account losing your coordinator during 2.9) and that during November, December and January, I don't think we will have much QA resources available. Also, we will have the Apereo Conference in June 2014, which might slow things down a tad. If I try working backwards from a May 15 date for a release, it just doesn't add up. 

The discussion will be for the CLE release team meeting tomorrow. 

Thanks!
Neal


Neal Caidin
Sakai CLE Community Coordinator
Skype: nealkdin
Twitter: ncaidin










_______________________________________________
cle-release-team mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/cle-release-team



_______________________________________________
sakai2-tcc mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
Neal Caidin-3 Neal Caidin-3
Reply | Threaded
Open this post in threaded view
|

Re: [sakai2-tcc] [cle-release-team] Sakai 2.10 schedule - strawperson

How does this relate to the 2.9/2.10 list of planned issues plus discussion at Open Apereo figure into this, if at all?  We've had some email discussion on most (not all) of these items, but not sure if we just move forward or something definitive needs to come out of it. 

Dashboard

LinkTool  ( believe Anthony will be proposing to decommission this for 2.10 )

Yale Signup Contrib

News vs News Feed vs Swinsburg portal solution - https://wiki.jasig.org/display/PLT/Simple+RSS+Portlet?desktop=true

Roster2 vs Roster

Portal Chat on by default

Spring Annotations ( saw positive support for this and no objections on email thread)

and maybe a couple of more…

Thanks,
Neal



Neal Caidin
Sakai CLE Community Coordinator
Skype: nealkdin
Twitter: ncaidin









On Oct 2, 2013, at 10:59 AM, Matthew Jones <[hidden email]> wrote:

I think this sounds good, but I'm a little more optimistic about the dates.

We're planning on a feature identification freeze this week. This includes all features that have patches attached which are desired for 2.10. Some of these will require manual conflict resolution to update from older patch code so will take awhile. The actual feature merge work should be done by the end of October which would be the true feature freeze. Then after all outstanding blockers are resolved we can cut the branch and the first alpha by mid-late November. It should be done prior to Thanksgiving as has been stated in the past, so by Friday November 22.

I don't think we'll be on Alphas all the way until March. The Alpha process is mostly waiting for translation to complete and resolving issues found in QA so it could be variable but I don't anticipate any seriously time consuming issues. With the unconference at the end of January, I'd put Beta 01 in early February rather than early March, with the presumption that at least a few people who can work on the release will be present and working to finish out whatever is needed for Beta at the unconference. That could bump the other dates up by a month which would be ideal, given the date of the Juneconference, and the 6 month release schedule of the 2.8 release which was a more typical schedule than 2.9.

On Wed, Oct 2, 2013 at 10:31 AM, Neal Caidin <[hidden email]> wrote:
[ CLE release team and PMC (formerly known as TCC)]

We need to come up with a schedule for 2.10.  

Strawperson [for discussion] - High level milestone targets

-------------------------------------------------
2013 mid-Oct  - Scope Freeze
2013 late-Nov  - Branch cut - Alpha 01
2014 early-March - Beta 01
2014 early-May - RC01
2014 mid-July - GA (General Availability aka production)


This seems to me like a realistic schedule, based on looking at the actual schedules for 2.8 and 2.9 (and taking into account losing your coordinator during 2.9) and that during November, December and January, I don't think we will have much QA resources available. Also, we will have the Apereo Conference in June 2014, which might slow things down a tad. If I try working backwards from a May 15 date for a release, it just doesn't add up. 

The discussion will be for the CLE release team meeting tomorrow. 

Thanks!
Neal


Neal Caidin
Sakai CLE Community Coordinator
Skype: nealkdin
Twitter: ncaidin










_______________________________________________
cle-release-team mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/cle-release-team




_______________________________________________
sakai2-tcc mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc