[cle-release-team] Sakai 10.0 Branching

[Neal Caidin]

Sure (though I'm not Sam, in case you couldn't tell).  That is where we 
were heading. We started the last meeting by reviewing the tools and 
blocker issues to identify gaps in what was needed to cut a qa03.  We 
didn't make it through all of the blockers though.


here is this week's agenda ,... being formed...

http://etherpad.ctools.org/rmmt-2014-02-06

I think one of the options is to consider cutting out some of the scope. 
So we should start thinking about things like, if if the News tool 
replacement is not done, perhaps we should move forward with Sakai 10 
without it, and put in either a Sakai 10.x or Sakai 11? The MathJax work 
perhaps isn't quite done so maybe that gets pushed out? Etc. Now would 
be the best time to make these decisions to avoid scope-drag.

My sense was that, in general, we were trying to prioritize the schedule 
over the scope. If so, now may be the time to make those tough 
decisions. We had our feature cutoff on January 18, and now we might 
need to cement this for Sakai 10 if we are to have a reasonable chance 
of meeting our target dates.

We also need to identify branch managers for Sakai 10 and Sakai 2.9, and 
maybe give some thought to Sakai 2.9.x management (i.e. will we be 
focusing only on critical issues  or possibly a 2.9.4 , with lots of 
merges having already taken place and more available).

2 cents.

-- Neal


> Kirschner, Beth <mailto:bkirschn at umich.edu>
> February 4, 2014 at 3:39 PM
> Hi Sam -- can you add when to branch to Thursday's agenda? I'd propose 
> that we should branch as soon as we have the News tool replaced. I 
> worry that the longer we wait to branch, that the risk of having new 
> bugs/features introduced is greater than the effort to merge bug fixes 
> from trunk to a branch.
>
> Thoughts?
> - Beth
>
> On Feb 4, 2014, at 12:53 PM, Neal Caidin <neal.caidin at apereo.org 
> <mailto:neal.caidin at apereo.org>> wrote:
>
>
> Neal Caidin <mailto:neal.caidin at apereo.org>
> February 4, 2014 at 12:53 PM
> Many things were not in place to proceed.
>
> http://etherpad.ctools.org/rmmt-2014-01-30
>
> It sounded like there were some tools that need license file source 
> headers applied; a number of tools were not moved from Contrib yet 
> into core; the new News tool is not ready yet; and OSP status is not 
> fully resolved. Plus a fair number of blockers, though I'm not clear 
> if they are blockers with respect to cutting a qa03 or with respect to 
> the first release candidate.
>
> This is a missed milestone and I'm not sure exactly how far behind we 
> are (hopefully no more than a week or two). Realistically, our 
> schedule will need to be re-targeted.
>
>
> -- Neal
>
>
>
> Kirschner, Beth <mailto:bkirschn at umich.edu>
> February 4, 2014 at 12:26 PM
> What is the current plan for branching Sakai 10.0? It looks like we've 
> reconsidered the goal of branching at the end of last week? I'm 
> worried that if we don't branch soon, it will impact our ability to 
> put out a stable release this Spring.
>
> - Beth
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team

-- 
Neal Caidin
Sakai Community Coordinator
Apereo Foundation
neal.caidin at apereo.org
Skype me! (but let me know in advance for the first interaction) - nealkdin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140204/678a3238/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1196 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140204/678a3238/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20140204/678a3238/attachment-0001.jpg