[Building Sakai] Merging trunk portal chat back to 2.9.x

[Aaron Zeckoski]

I think that for the sake of QA not going crazy and for tracking
puporses and the stability of 2.9, it would ideal to have something to
refer to in JIRA but I will let others sound off on this.
:-)
-AZ


On Thu, Oct 4, 2012 at 8:18 AM, Adrian Fish <adrian.r.fish at gmail.com> wrote:
> No JIRA for the chat.js change, sorry.
>
> The JIRA for moving the entity provider into a webapp is SAK-22741, that
> catches the provider change that went with the js fix. So, to sum up, if
> SAK-22741 is merged to 2.9.x, chat.js still needs to go in. I can JIRA that
> as a separate issue affecting 2.9.x, not trunk, and attach a patch, if
> that's better.
>
> Cheers,
> Adrian.
>
>
> On 4 October 2012 15:14, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>>
>> What's the JIRA for this?
>> -AZ
>>
>> On Thu, Oct 4, 2012 at 6:56 AM, Adrian Fish <adrian.r.fish at gmail.com>
>> wrote:
>> > I fixed a showstopper bug in portal chat which flagged everybody up as
>> > 'offline' when they weren't.
>> >
>> > I'd like to merge portal/portal-chat back to 2.9.x and modify both
>> > portal/pom.xml (just the modules bit as portal-chat only has a tool now)
>> > and
>> > portal-charon/charon/src/webapp/scripts/chat.js to sort out the offline
>> > flag. This will only affect portal chat, not the rest of the neoportal -
>> > the
>> > risk is low.
>> >
>> > I can do this and test it but really it should be a branch manager. Is
>> > everybody ok with me doing this?
>> >
>> > Cheers,
>> > Adrian.
>> >
>> > _______________________________________________
>> > 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"
>>
>>
>>
>> --
>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>
>



-- 
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile