[sakai-core-team] Sakai 10.0 release notes

[Neal Caidin]

I'm going with Seth's suggestion to keep the same wording as in Sakai 
2.9, with appropriate version number changes, since nobody else has 
chimed in .

Thanks,
Neal


> Neal Caidin <mailto:neal.caidin at apereo.org>
> June 19, 2014 at 1:22 PM
> Okay, I mentioned because I was hearing that we strongly are 
> encouraging the community to move to Sakai 10.
>
> [1] If we say "... strongly encouraged to upgrade to the latest 
> versions of Sakai 2.9 or Sakai 10 in order to take advantage of 
> continued maintenance support."
>
> Perhaps it should be something like this:
>
> [2] "With the advent of the Sakai 10 series, official Community 
> support for Sakai 2.8 ceases. The latest versions of Sakai 10 and 
> Sakai 2.9 are the community supported releases. Organizations running 
> Sakai 2.8 and earlier versions are strongly encouraged to upgrade to 
> Sakai 10 in order to take advantage of numerous improvements and 
> continued maintenance and support."
>
> The phrasing in [2] explicitly acknowledges that Sakai 2.9 is 
> supported, but encourages Sakai 10 adoption more explicitly.
>
> Does that seem better, or don't rock the boat and just stick with the 
> original phrasing [1] ?
>
> Thanks,
> Neal
>
>
>
>
>
> Seth Theriault <mailto:slt at columbia.edu>
> June 18, 2014 at 2:01 PM
>
> No, we never say "deprecated." We only announce the end of support for
> the n-2 version.
>
> For example, from the 2.9.0 release page:
>
> "With the advent of the Sakai 2.9 series, official Community support
> for Sakai 2.7 ceases. Organizations running Sakai 2.7 (or earlier
> versions) are strongly encouraged to upgrade to the latest versions of
> Sakai 2.8 or 2.9 in order to take advantage of continued maintenance
> support."
>
> (http://source.sakaiproject.org/release/2.9.0/)
>
> Seth
>
> Neal Caidin <mailto:neal.caidin at apereo.org>
> June 18, 2014 at 11:07 AM
> Hi PMC,
>
> I've been working on updating the technical requirements for Sakai 
> 10.0 with the help of the Sakai core team. It occurs to me that it 
> might be good for the PMC to review the documentation [1, 2] as it 
> relates to policy decisions and messaging. To me the most important of 
> these is probably the message we want to send about supporting past 
> releases of Sakai?
>
> Here is my draft message:
>
> With the advent of the Sakai 10 series, official Community support for 
> Sakai 2.8 ceases and 2.9 is deprecated. Organizations running Sakai 
> 2.9 and earlier versions are strongly encouraged to upgrade to Sakai 
> 10 in order to take advantage of numerous improvements and continued 
> maintenance and support. Sakai 2.9 will continue to receive critical 
> security patches and selective fixes.
>
>
> This is my proposed wording. Do we want to say that 2.9 is deprecated 
> when Sakai 10 is released? My thinking is that we want to encourage 
> everyone to move to Sakai 10 and that this reflects the reality of our 
> resource levels and focus? But maybe there are downsides to this 
> message, or phrasing it this way, and we should just mention that 
> community support for 2.8 ceases? Should we mention that if you are on 
> Sakai 2.9, it should be the 2.9.3 version? etc.
>
> Thanks,
> Neal
>
> [1] Confluence Release notes - 
> https://confluence.sakaiproject.org/pages/viewpage.action?pageId=86245732
> [2] Technical Release notes - 
> https://source.sakaiproject.org/release/10.0/
>
>

-- 
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/sakai-core-team/attachments/20140623/384dc4fe/attachment.html 
-------------- 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/sakai-core-team/attachments/20140623/384dc4fe/attachment.jpg