[sakai-pmc] Sakai 10.0 Schedule

Wed Dec 4 10:36:26 PST 2013

1) Both of those are fine. I just think we weren't sure with what phase
we're in right now. Probably just nothing really specific. QA numbering
would being at the end of January.

2) So that gives us either 3 or 4 cycles (QA RCs) of 2 weeks between March
13th or March 27th (the most likely dates for RC), if you were planning it
out in that detail. I agree that generally the decisions were made on
Thursday and the release was done on Friday or Monday. I think the new
process of release means that it will be able to be out on Friday a lot
easier than in the past.

On Wed, Dec 4, 2013 at 1:12 PM, Kirschner, Beth <bkirschn at umich.edu> wrote:

> On Dec 4, 2013, at 1:03 PM, Neal Caidin <neal.caidin at apereo.org> wrote:
>
> > Okay, I’ve updated the schedule portion of -
> https://confluence.sakaiproject.org/display/REL/Sakai+10+Release+Schedule+and+Scope.
> >
> > Two things:
> >
> > 1) I thought we decided not to use the Alpha/Beta terminology and just
> use QA01 … QAn (where n is an integer) until we hit the first Release
> Candidate?  My labeling reflects the QAn naming convention.
> >
> Ok - I had forgotten
>
> > 2) My main concern with the schedule, at the moment, are expectations of
> 2 week QA cycles and Bug Fix cycles. It seems like we are anchored on
> Thursday’s Sakai release calls (aka CLE release calls, at least in the
> past), so if we miss a Thursday window it seems like it that kind of
> movement gets pushed out a week, if you catch my drift.
> >
> I'm not quite sure I catch your drift - but I think what you have in place
> is a good starting point for discussion on Thursday's CLE/release team call.
>
> Thanks!
> - Beth
>
> > Thanks,
> > Neal
> >
> >
> >
> >
> >
> > Neal Caidin
> > Sakai Community Coordinator
> > neal.caidin at apereo.org
> > Skype: nealkdin
> > Twitter: ncaidin
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Dec 4, 2013, at 11:25 AM, Kirschner, Beth <bkirschn at umich.edu> wrote:
> >
> >> Hi Neal,
> >>
> >> I'd suggest updating the confluence page with the changes that Matt and
> I have suggested (I agree with Matt on the timing of the beta vs RC). If
> you could get this out soon, perhaps it could be discussed on the Thursday
> release team call?
> >>
> >> - Beth
> >>
> >> On Dec 4, 2013, at 11:10 AM, Neal Caidin <neal.caidin at apereo.org>
> wrote:
> >>
> >>> Sounds good.
> >>>
> >>> Can I have some help in developing a more detailed schedule? If I send
> out a Doodle for next week, would I get some takers?
> >>>
> >>> Some thoughts:
> >>> - Shooting for organized testing for the couple of weeks, as you’ve
> seen by other emails.
> >>> - Can remind folks that we are at feature proposal freeze this week. I
> think we should have another milestone, before Jan 30, for scope freeze.
> >>> - Need to also communicate that new features not going into Sakai 10 ,
> need to create their own branch.
> >>> - We should have a transparent process for making decisions if new
> stuff crops up that we are not expecting during this process.
> >>>
> >>> Thanks,
> >>> Neal
> >>>
> >>>
> >>>
> >>> Neal Caidin
> >>> Sakai Community Coordinator
> >>> neal.caidin at apereo.org
> >>> Skype: nealkdin
> >>> Twitter: ncaidin
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On Dec 4, 2013, at 10:33 AM, Matthew Jones <matthew at longsight.com>
> wrote:
> >>>
> >>>> Yea, I've mentioned to Neal to that it would be good to have some
> kind of spreadsheet like the 2.9 [1] one up on confluence. Megan and I
> mostly maintained that one, and it wasn't guaranteed to be entirely
> accurate while working on it , but in the end it was correct and it gave
> people a rough idea of what to expect.
> >>>>
> >>>> I think the schedule you proposed below and the write-up is what
> we're aiming for. I believe all features have been identified on SAK-24197
> that either are in or that we'd like to have in prior to the beta (if
> someone puts the effort into getting them in). There are a few new tools
> mentioned over the past few weeks that some would also like to see
> included. I'm not sure yet if those are going to be in and stealthed,
> included as an experimental profile that you can build from source but not
> the binary (as they are now) or not in at all. This will be something we
> work out over the next few weeks I'd bet.
> >>>>
> >>>> The first "pre-release"was cut and put on qa on 11/15. Since then
> there has been a lot of bug and security fixes so this feels out of date
> already. There are also some cleanup blockers involving old code cleanup
> and conversion scripts, so it's still very pre-release at the moment.
> >>>>
> >>>> I think the biggest ??? in the schedule will be the time between beta
> (the branch cut) and RC as we have no specific date/event *yet* for a
> ribbon cutting pow-wow like we do with the beta. I feel like it won't take
> more than 2 months, but that could put it anytime in March, and 03/07, 5
> weeks after beta, seems a few weeks optimistic to me at the moment,
> especially with schools getting ready for spring/summer terms. I believe
> the time between beta and RC would be longer than RC and release, since we
> should be good to go for RC. So the only change I'd make is that RC is more
> likely at the end of March (around 8 weeks, so 3/21 or 3/28) then we'd set
> a goal for the release prior to Learning Impact (which is May 5th). RC
> should really be good to run with very minor changes before cutting the
> first release. Then we'd have a month to even get out a .1 release if
> anything does come up for early adoptors prior to the Sakai conference.  We
> had some clients running the 2.9 RC last year. (When it came out in
> September 2012) and I don't remember any huge problems aside from
> performance in a few tools.
> >>>>
> >>>> Many of Longsight clients have been asking about the new release so
> if this is good to go we'd likely be doing upgrades next summer for most
> like last summer for 2.9. I'm not sure if we'd have anyone ready to go by
> May. We've merged back many of the new features that are going in to 10
> into local forks so going to 10 won't be nearly as huge a change as the
> upgrade from 2.7 or 2.8 was, but there are looking like some solid
> improvements that didn't make it back into the branches. The changes in the
> build process should make this release much easier to deploy and maintain
> too. Aside from trying to deal with RSF in github, I've been pretty happy
> with building 10. ;)
> >>>>
> >>>> I'd like to see some target dates for beta, and release-candidate
> tags put into the schedule as well. I think if we aim to have a mid-May
> general release we will end up having the release in June. A June release
> will be too late for most institutions to adopt over the (northern
> hemisphere) summer. I think we should challenge ourselves to put out a
> release in April.
> >>>>
> >>>> UM would like to help with QA, load testing, and if the release looks
> stable, a summer production deployment. What other institutions are
> considering Sakai 10? I think we need to know who the early adopters are.
> >>>> Ideally what I'd like to see is something like this:
> >>>> -----------------------------------------------------
> >>>> Dec 06 cutoff for new feature proposals for Sakai 10
> >>>> Jan ?? Sakai 10.0 first test-a-thon
> >>>> Jan 30 Sakai 10.0 branch cut at Apereo Boot Camp (beta 01)
> >>>> Jan 30 String freeze
> >>>> Feb ?? QA test-a-thon
> >>>> Feb 14 Beta 02
> >>>> Feb ?? QA test-a-thon
> >>>> Feb 28 Beta 03
> >>>> Mar ?? QA test-a-thon
> >>>> Mar 07 Release Candidate 01
> >>>> March/April release candidates every 2 weeks (with test-a-thons
> in-between)
> >>>> Apr 30 Production Release
> >>>> -----------------------------------------------------
> >>>>
> >>>> [1]
> https://confluence.sakaiproject.org/display/REL/Sakai+2.9.0+Release+Schedule
> >>>> _______________________________________________
> >>>> sakai-pmc mailing list
> >>>> sakai-pmc at collab.sakaiproject.org
> >>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
> >>>
> >>
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131204/282bf01b/attachment.html 