[cle-release-team] 2.9.0 key issues [short] list

[Matthew Jones]

It doesn't appear as if it's known. SAK-20521 upgrade Quartz from 1.5.2 (A
2006 release) to 1.6.6 (A 2009 release) so this is the most likely cause,
but reverting this would probably not be possible. Finding out the fix
would certainly be a good thing though, or it would have to be pretty well
documented if we were planning on holding off till 2.9.1.

On Tue, Oct 30, 2012 at 9:19 AM, May, Megan Marie <mmmay at indiana.edu> wrote:

> #1 - seems fine to me
>
> #2 - Ok - as long as the documentation reflects this
>
> #3 -  seems especially bad to me.   Do we know what introduced this issue?
>   If fixing doesn't seem to resolve the problem, what about rolling out the
> changes that caused this?
>
> Megan
>
> -----Original Message-----
> From: cle-release-team-bounces at collab.sakaiproject.org [mailto:
> cle-release-team-bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin
> Sent: Tuesday, October 30, 2012 8:54 AM
> To: cle-release-team at collab.sakaiproject.org
> Subject: [cle-release-team] 2.9.0 key issues [short] list
> Importance: High
>
> Hi All,
>
> Summary
> ------------------
> We have a few issues that would normally be blockers. I am proposing the
> we proceed forward with the release and address these in 2.9.1 .
>
>
> Details
> ------------------
> These would normally be blockers, but given how close we are to the
> release, we will not treat them as blockers with respect to the 2.9.0
> release.
>
> 1) Updated Help files for the context sensitive Sakai Help system are not
> going to be in 2.9.0 . At the last CLE team meeting we had consensus that
> if this were to happen (there was still a sliver of hope at the time that
> we could get the Help files updated), it would not be a blocker for 2.9.0 .
>  It turns out that the technical requirements for updating Help files are
> significant. If we tried to get Help files into the release from this point
> it would probably delay us till December. There is no Jira for this issue
> (maybe there should be?).
>
> 2) https://jira.sakaiproject.org/browse/SAK-22845  - NeoChat not working
> .  This just came in this morning and would normally be a blocker, but I
> propose that we move forward, especially since NeoChat is a new feature,
> turned off by default, and therefore not a regression (correct?)
>
> 3) https://jira.sakaiproject.org/browse/SAK-22801 - Regression: Fired
> Triggers causes startup to crash. This one is a pain, but there is a
> workaround for the problem. Would still normally be considered a blocker,
> in my opinion.
>
>
> Does anybody disagree with the proposal to move forward with the 2.9.0
> release?  I would like to hear concerns in advance of Thursday's call, if
> at all possible, especially given our tight timeline.
>
> FYI, I'll highlight these as the top 3 known issues in the release
> documentation.
>
> Thanks,
>
> Neal Caidin
>
> Sakai CLE Community Coordinator
> nealcaidin at sakaifoundation.org
> Skype: nealkdin
> AIM: ncaidin at aol.com
>
>
>
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20121030/72c0c156/attachment-0006.html