[sakai-pmc] [sakai-core-team] Sakai 11 status and planning - discussion

[Neal Caidin]

We discussed Sakai 11 on the Sakai Core team call yesterday.

In my opinion we should proceed with committing to Sakai 11 with Morpheus
and developing a schedule. Having a schedule and milestones helps many in
the community with both their institutional planning and their planning for
involvement in Sakai QA and in contributing their patches back to trunk.
And it helps give core team members extra motivation as well.

We discussed the possibility of a 10.5 release with some of the trunk
features, with the main advantage being that we could get a release out for
summer (northern hemisphere, june/july). Some of those features include
Samigo performance enhancements, the new Dashboard tool, potentially the
Lessons Enhancement Project (LEaP) Phase 1, potentially the new Gradebook
spreadsheet entry functionality, etc. However, the timeline for some of
these features aren't clear yet. Samigo performance enhancements are done
(I think) and Dashboard is on in trunk, so that's good.

We discussed that it is getting harder and harder to merge back from trunk
to the Sakai 10 branch because they are diverging so much , and in some
cases fixes in Sakai 11 have to be rewritten to work in 10, plus additional
QA required. To me, among other things, that is an argument against having
a 10.5 that has significant new features. I worry it would be a bit of a
Frankenstein, and like the fabled monster, hard to manage.

On the other hand, Morpheus isn't quite ready yet, and it would make it
easier to plan if the other tool improvements were further along (checked
into trunk, etc). Makes it difficult to have a firm schedule.

I still think we can have a tentative schedule, which we know we will have
to revisit once things are further along in these projects, but it could be
a great starting point.

2 cents and a cup of coffee.

Neal




On Mon, Jan 26, 2015 at 12:31 PM, Adam Marshall <adam.marshall at it.ox.ac.uk>
wrote:

>  I think you are 100% spot on. Morpheus has to be in Sakai 11.
>
>
>
> adam
>
>
>
> --
>
>
>
> ** Note change of email address to adam.marshall at it.ox.ac.uk **
>
>
>
> Dr A C Marshall, WebLearn Service Manager, University of Oxford.
>
> IT Services, 13 Banbury Rd, Oxford. OX2 6NN.
>
>
>
>
>
> *From:* sakai-core-team-bounces at collab.sakaiproject.org [mailto:
> sakai-core-team-bounces at collab.sakaiproject.org] *On Behalf Of *Neal
> Caidin
> *Sent:* 26 January 2015 17:07
> *To:* sakai-pmc at collab.sakaiproject.org;
> sakai-core-team at collab.sakaiproject.org
> *Subject:* [sakai-core-team] Sakai 11 status and planning - discussion
>
>
>
> [sakai-pmc, sakai-core-team]
>
>
>
> Hi All,
>
>
>
> I thought it would be good to continue the discussion regarding Morpheus,
> Sakai 11, and the schedule with PMC and Sakai core team lists before moving
> to the sakai-dev list. So here it is.
>
>
>
> Morpheus is making great progress and we should see some commits coming
> into Github from Mark Reilly, probably this week. There is also some
> discussion of a sprint in February.
>
>
>
> My perception is that we are heading to a decision that our release
> schedule should be based on Morpheus and the QA effort that will be
> necessary to make this successful. I am leaning towards proposing this
> "officially" so that we can firm up the schedule. Given that Morpheus is
> not fully baked yet, and that there will need to be a large QA testing
> effort, I would forecast we would complete Sakai 11 in Q4 2015. There is no
> harm in setting a target of early August so that if we make fast progress,
> one of our early adopters could launch in Fall 2015.
>
>
>
> I've started a Pros and Cons and Assumptions Google doc
>
>
>
> http://bit.ly/1uRoOgq
>
>
>
> Interested in hearing what you think.
>
>
>
> Thanks!
>
> Neal Caidin
>
> Sakai Community Coordinator
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20150130/ca9a7ab3/attachment.html