[sakai-pmc] [cle-release-team] input requested - Sakai 2.10 schedule

Wed Oct 16 11:04:01 PDT 2013

I think that Sakai 2.9 could have legitimately been bumped up to a new
major version and called something different mostly because of completely
new UI. For the next release we'd talked about removing the old portal and
making this the only portal (since that other one is maintained).. Though
whatever happens with this really feels like it will have to bump the
version number even if just for technical reasons but also because this
might be the biggest release yet. And that's even without pulling in any
new tools. It's far from a few fixes once you start looking through just
the features.

https://jira.sakaiproject.org/issues/?filter=13771

Build/technical issues
- None of the contrib tools will work anymore, hibernate and spring
dependencies all changed so minimally new profiles that take this into
account will be necessary.
- Along with those dependencies, these newer libraries including support
for JSF 2.0 are pretty major upgrades. Sure it's not a jump all the way to
hibernate 4, but it is a lot of needed modernization.
- The flattening of indies will also change the build process, possibly
changing how a lot of people do things, since there are no properties in
master. This includes the release team

New features (that I can think of at the moment)
- First revision for Keitai across tools almost doubles the number of
direct endpoints available (Though I still feel we should have some
resolution on SAK-21959 either a defined version or no direct api changes
allowed in a minor release)
- Assignment/Samigo/Site Management/Forums have all had substantial
improvements and new features. Lessons is has a lot of new changes in the
new version for import/export.
- Support for LRS and Tin Can API built in and across many tools, hard to
back-port
- iSyllabus as part of the core with improved linking.
- Restoration of deleted files and sites with all UI elements incorporated
- CKEditor 4.x with new plugins including audio recording and support for
plugins on CKEditor.com (most aren't supported in 3.x)
- Elastic Search support is much improved over current search
- New language support, including significant update for German

Probably a lot more that I'm missing right now.

On Mon, Oct 14, 2013 at 8:18 PM, Steve Swinsburg
<steve.swinsburg at gmail.com>wrote:

> I purposely removed the main lists from this reply. Regarding the name of
> Sakai 4 etc, I dont think anyone agreed that this would be related to 2.10
> in its current form. The idea behind Sakai 4 was a big m major release with
> lots of new functionality. 2.10 was to get the current functionality out
> there.
>
> Personally I think that putting 2.10 out with just a few fixes is
> pointless and we should slow down slightly, discuss the proposals that no
> one has agreed upon but have been out there for a long time and get some
> decent new functionality into the release. It would delay the cycle by a
> couple of months but at least gets an interesting release out there.
>
> I would like to see more of this discussion happening on list where
> everyone can view it and respond and not have discussions reserved for
> phone meetings.
>
> thanks,
> Steve
>
>
> On Tue, Oct 15, 2013 at 1:54 AM, Neal Caidin <neal.caidin at apereo.org>wrote:
>
>> [sakai-dev and cle-release and sakai-qa]
>>
>> Hi All,
>>
>> Your Input
>> -----------------------
>> Please feel free to chime in with your opinion and especially if you
>> think this is a good schedule or you have concerns about this schedule,
>> definitions, etc.. Your input is welcome and appreciated. Please copy all
>> the lists in your response? It helps maintain continuity in the discussion.
>>
>>
>> Background
>> -----------------------
>> There has been some initial conversation with the CLE release team (aka
>> Sakai team) and the PMC (previously known as TCC) about the 2.10 schedule.
>> It does seem like there is significant initial support for this schedule.
>>
>> First note: The final name for the release has not been determined. *For
>> convenience we are calling it the 2.10 release for now, but it could change
>> to something like Sakai 4.* Just a heads up.
>>
>> When the branch is created for 2.10, it will be an Alpha release. Some
>> recent discussion has been focused on determining the criteria to move from
>> an Alpha release to a Beta release.
>>
>> Here is the latest schedule which I'm suggesting. For those who've been
>> following, I've changed the Branch cut date from late-November to
>> mid-November, just to emphasize we need to get Alpha cut before (American)
>> Thanksgiving but essentially unchanged.
>>
>>
>> Proposed Schedule for Target milestones - Sakai 2.10
>>
>> -------------------------------------------------------------------------------
>> 2013 mid-Oct  - Scope Freeze (about now….)
>> 2013 mid-Nov (pre-Thanksgiving)  - Branch cut - Alpha 01
>> 2014 early-February - Beta 01 - criteria - no blockers
>> 2014  early- April  - RC 01
>> 2014 mid-May - GA (General Availability aka production)
>>
>>
>> QA Assumptions
>> -------------------------------
>> * Sufficient level of QA testers / testing available between phases.
>> * Anticipate the greatest need of QA testing to be from Beta 01 (February
>> 2014) through release (May 2014) … [doesn't mean we don't need QA testing
>> once Alpha is cut. We do!]
>> * Will need people to update Regression scripts to include new features
>> * Will need both Jira testing and Regression testing, but a lot more
>> focus on Regression! Ad hoc testing will be welcome (i.e. test features
>> that are important to your institution using your own methodology and
>> report back to QA lead. The more approaches and more eyes we get on the
>> release the better).
>> * Having some "synchronized testing" in which we will schedule time to
>> test together as a community, will be scheduled.
>>
>>
>> Proposed Definitions
>> ---------------------------------
>>
>> Scope Freeze - all the scope for the release identified. In all but rare
>> cases, the items identified for inclusion in the release should also be
>> resolved and fixed (Jira terminology) before the Alpha release is cut.
>>
>> Alpha - scope freeze defined, branch cut, blocker bugs fixed. It is
>> possible that new features could be added, BUT these features need to be
>> defined in the Scope freeze, and we should decide explicitly which features
>> should go in during Alpha phase. The default position is a feature which is
>> not resolved/fixed before Alpha is NOT in the release. Final strings
>> (button text, instructions, labels, etc.) defined during Alpha. String
>> freeze before Beta.
>>
>> Beta cut - moderate level of Alpha testing completed. Not only scope
>> freeze and implementation freeze for new features before cutting Beta. No
>> new features added during Beta. String translation occurs during Beta. Does
>> this mean that Online Help text is also frozen when we cut Beta (that seems
>> ambitious)?
>>
>> Release Candidate - All blocker and critical bugs fixed from Beta phase.
>> Release candidate means the release is close to ready for release (aka
>> general availability). At this phase, we only hold up moving to GA if
>> blocker bugs are found. What constitutes a blocker bug is implicitly held
>> to a higher level of impact to the release (stack traces, gradebook
>> calculation errors, etc. )
>>
>> GA - general availability of the release (aka production).  Tag is
>> created. Final immutable release.
>>
>>
>> Included in Scope so far:
>> ---------------------------------------
>> 1) Here are a list of proposed Patches for 2.10. A number have already
>> been merged:
>> https://jira.sakaiproject.org/browse/SAK-24197
>>
>> 2) Anything merged into trunk to-date (which means we may need to be more
>> conscious and thoughtful about additional merges in trunk between now and
>> Alpha so as not to increase the scope)
>>
>>
>> Open questions about Scope?
>> ------------------------------------------------
>> The PMC (formerly TCC) has a page with a number of items that had been
>> under consideration for 2.9/2.10.
>> https://confluence.sakaiproject.org/display/TCC/TCC+CLE+Action+Items
>>
>> From this several discussions have emerged, mostly on the sakai2-tcc
>> list, some on the sakai-pmc list, and sometimes the cle-release-team list
>> (sorry for the inconsistency, sakai-pmc is the latest, but a lot of
>> conversation occurred while PMC was still TCC). We should target THIS WEEK
>> to make a decision, if at all possible.
>>
>> I am not clear on the status of most of these items personally. Feel free
>> to take a look at the list archives and see what you think.
>>
>> a) Link tool -  may be a proposal to decommission the Link tool soon? LTI
>> addresses many of the use cases that Link tool used to handle?
>>
>> b) Yale Signup tool -  I think the main concern is support if we bring
>> this tool in? Does it fall to the CLE release team or is there another way
>> to support? That's what I was hearing. There is a lot of positive community
>> interest in the Yale sign up tool (#1 used Contrib tool based on the Sakai
>> Tool survey earlier this year).
>>
>> c) Roster 2 tool to replace Roster 1?  I'm not clear on status. Sounded
>> like there was not clear consensus to me.
>>
>> d) Spring Annotations - to me, I think I saw positive feedback on this
>> one and no objections/concerns.
>>
>> e) Portal chat on by default - not a clear outcome. I saw concerns about
>> performance if Portal chat was on by default, but a challenge to that
>> concern, saying there is no evidence of performance issues for portal chat.
>>  ?
>>
>> f) News feed tool to replace the News tool?  Nobody has stepped up to fix
>> the News feed tool to get it in shape. Sounds like it is a better tool than
>> the News tool and over time, probably about the same level of maintenance
>> (I'm personally not familiar with differences). Steve Swinsburg offered his
>> portlet as a replacement -
>> https://wiki.jasig.org/display/PLT/Simple+RSS+Portlet
>>
>> g) Retire Profile for Profile 2 - Mostly Profile 2 is the main tool but
>> Profile still exists due to dependencies?
>>
>> Thanks for your help!
>>
>> Check September and October archives for discussions
>>
>> -----------------------------------------------------------------------------------
>>
>> http://collab.sakaiproject.org/pipermail/sakai2-tcc/
>>
>> http://collab.sakaiproject.org/pipermail/sakai-pmc/
>>
>>
>> Cheers,
>> Neal
>>
>>
>>
>> Neal Caidin
>> Sakai CLE Community Coordinator
>> neal.caidin at apereo.org
>> Skype: nealkdin
>> Twitter: ncaidin
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> cle-release-team mailing list
>> cle-release-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>
>>
>
> _______________________________________________
> 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/20131016/fc1852f6/attachment.html 