[cle-release-team] [Building Sakai] Release thoughts

[Matthew Jones]

Right we talked about this on the call this morning. We eventually will
have a freeze for i18n and help documentation. This is planned to be the
beta which we'd like to happen at the ApereoCamp at the end of January.

Some date between now and January (ideally in the next few weeks) we will
have all blockers resolved and will be able to cut an "alpha". This will be
deployed to some QA server where and better testing can start on a stable
database with a static revision. This is what Neal mentioned in his email.
Trunk will still be getting new features planned for merged 10 in. Any new
feature that is decided to not be included in Sakai 10 (likely because of
the amount of work remaining or the large possibility of regression) will
need to be held off in a branch or in a patch file.

There's some details still to be worked out and will be sent out in a more
formal announcement in the next few weeks.

On Wed, Nov 13, 2013 at 7:35 AM, Mark Breuker <mbreuker at loi.nl> wrote:

>  It's also important to have a moment in time where the translators can
> start their work. If the functionality is still changing (strings being
> added, removed and rearranged) you are trying to translate a moving target.
> If string freeze occurs at the creation of the beta branch that's ok but it
> should be very clear to the i18n community.
>
>  - Mark
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20131113/8986406a/attachment-0001.html