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

[Sam Ottenhoff]

Adrian,

Should I revert this change in the 2.9.x branch?

--Sam

On Tue, Oct 30, 2012 at 11:36 AM, Fish, Adrian <a.fish at lancaster.ac.uk>wrote:

>   That's obviously my bad. I was working on the portal chat testing with
> Chuck and Juan and wanted to shorten the test cycle by not forcing Chuck to
> have to restart his test cluster every time I made a change to the entity
> provider. It should have been in a webapp from day one, to be honest, but
> there you go. Apologies for making work, Matthew. I'll take a look now.
>
>  Sorry,
> Adrian.
>
>  ==================================
> Adrian Fish
> CIS Analyst / Programmer
> ISS Building
> Lancaster University
> Lancaster, LA1 4YW
>
>  http://www.lancs.ac.uk
> http://www.sakaiproject.org
> http://confluence.sakaiproject.org/display/YAFT/Yaft
> http://confluence.sakaiproject.org/display/CLOG/Home
>
>   From: Matthew Jones <matthew at longsight.com>
> Date: Tue, 30 Oct 2012 11:08:43 -0400
> To: Neal Caidin <nealcaidin at sakaifoundation.org>, Adrian Fish <
> a.fish at lancaster.ac.uk>
> Cc: "May, Megan Marie" <mmmay at indiana.edu>, "
> cle-release-team at collab.sakaiproject.org" <
> cle-release-team at collab.sakaiproject.org>
> Subject: Re: [cle-release-team] 2.9.0 key issues [short] list
>
>  As far as #2, I believe that the refactoring of chat and the merge into
> rc02 is the most likely thing to break this. (SAK-22741)
>
>  Because portal chat used to be in a module called portal-chat
> "pcservice" which was removed from the source but not removed from the
> assembly, it caused me about an hour of additional work and head scratching
> when I tried to do the rc02 release. I had to fix this so the build would
> go through (SAK-22741) but I wasn't sure if portal chat would still work or
> not.
>
>  My guess is that if it's not working then the refactor was still pulling
> assemblies from the old portal chat and wasn't entirely fixed in trunk so
> should be broken everywhere.
>
>  I don't have time to look at it, but we can either revert SAK-22793 and
> SAK-22741 or someone else can fix it.
>
> On Tue, Oct 30, 2012 at 10:06 AM, Neal Caidin <
> nealcaidin at sakaifoundation.org> wrote:
>
>> I don't think anyone other than David Horwitz has had a chance to look at
>> #3 . David thinks it is possible to release with this, but not such a great
>> thing. He is most worried about possible impact on support.
>>
>> -- Neal
>>
>> On 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
>>
>
>
> _______________________________________________
> 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/20121031/8a8ca4ff/attachment-0006.html