[Building Sakai] Change the Sakai CLE release date policy ?

[Neal Caidin]

Yeah, plus what Sam says.

I was speaking about the official tagged releases, but the bug fixes in the
branches are ongoing. And even mix-and-match happens in which institutions
can easily apply patches for particular fixes if they do not want the whole
maintenance branch. Lots of options.


-- Neal




On Wed, Aug 6, 2014 at 11:59 AM, Neal Caidin <neal.caidin at apereo.org> wrote:

> >"Frequency of Updates. Sakai has not had significant updates in years
> (only bug fixes), and the fixes that do occur are annual, which is not
> frequently enough. The LMS candidates that we are investigating update
> tools, add functionality, and address bugs much more frequently."
>
> Yeah, that is clearly not a true statement. We have had lots of tool
> updates over the last couple of years and plan many more for Sakai 11.
> Major ones, not just minor tweaks. I was hoping to edit this video
> recording of a recent presentation a little better before sending out the
> link, but this includes a good summary of Sakai 10 release and the Sakai 11
> roadmap [1].
>
> I'm not seeing in your links where Moodle guarantees 2 month release
> cycles for maintenance releases?
>
> Our maintenance release cycle depends on a number of factors, needs of
> Sakai institutions based on feedback and collective knowledge and
> understanding of the academic calendar (which is tricky, since it varies),
> Sakai developer availability to fix bugs, community resources for QA
> testing, and, of course, the results of testing (e.g. if we find a new bug
> during QA testing, we need more time to get the bug fixed and retest).
>
> [1] Sakai 10 release and the Sakai 11 roadmap -
> https://www.youtube.com/watch?v=ibeiIyNwPUY&list=UUzDbnWaP_5kd6HpvDUjoT4Q
>
> Cheers,
> Neal
>
>
>
> On Wed, Aug 6, 2014 at 11:36 AM, <yleny at laposte.net> wrote:
>
>>
>> Hello,
>>
>> Maybe Sakai CLE developpers need to change the release date policy
>> because of this example :
>> I found this blog post when I made research about Sakai CLE and I think
>> that Sakai CLE developpers need to read it to improve Sakai CLE for a
>> better LMS for the users.
>>
>> The LMS Transition Initiative
>> http://wheel.ucdavis.edu/lms/
>> extract :
>> "Frequency of Updates. Sakai has not had significant updates in years
>> (only bug fixes), and the fixes that do occur are annual, which is not
>> frequently enough. The LMS candidates that we are investigating update
>> tools, add functionality, and address bugs much more frequently."
>>
>> When you take a look at all official releases of Sakai CLE web page (that
>> I have created), grouped by branch in reverse chronological order:
>> Sakai Release Date list
>> https://confluence.sakaiproject.org/display/DOC/Sakai+Release+Date+list
>> you can see that users neeed to wait 3 months for a minor release (2.9.x)
>> and 10 months between a major release (from 2.9.3 to 2.10.0) and  it's only
>> 2 months between a minor release for Moodle.
>> All official releases of Moodle, grouped by branch in reverse
>> chronological order:
>> http://docs.moodle.org/dev/Releases
>>
>> For the to support policy, you can compare these two tables :
>> For Moodle  :
>> https://en.wikipedia.org/wiki/Moodle#Releases
>> and
>> for Sakai CLE
>> https://en.wikipedia.org/wiki/Sakai_CLE#Releases
>>
>> Is it possible to have a minor release every two months to fix the bugs,
>> to have minor improvements and to have the latest translations ?
>>
>> Best regards
>>
>> Yannick
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140806/30feedbe/attachment.html