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

Neal Caidin nealcaidin at sakaifoundation.org
Thu Oct 4 10:52:43 PDT 2012


Thank you for creating a Jira ticket!

I notice the merge flag is set 2.9.x on 

https://jira.sakaiproject.org/browse/SAK-22743 but not for 

https://jira.sakaiproject.org/browse/SAK-22741 , please set the merge flag for SAK-22741 if it needs to get into 2.9.0 . And it looks like you've tested and verified 22741 but not 22743. If you have tested 22743 please click Tested, or include a test plan so that QA can jump in and help. :-)

Thanks,
Neal



On Oct 4, 2012, at 12:04 PM, Adrian Fish <adrian.r.fish at gmail.com> wrote:

> I've jira'd the js issue at SAK-22743. If that and SAK-22741 are merged into 2.9.x that should do the trick. If somebody does do it, if they drop me a line I'll test it.
> 
> Cheers,
> Adrian.
> 
> On 4 October 2012 16:56, Adrian Fish <adrian.r.fish at gmail.com> wrote:
> I'll see if I can tidy things up a bit.
> 
> 
> On 4 October 2012 16:37, Aaron Zeckoski <azeckoski at unicon.net> wrote:
> 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
> 
> 
> _______________________________________________
> 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"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20121004/1d8e6340/attachment.html 


More information about the sakai-dev mailing list