[Building Sakai] Blackboard work

[Matthew Jones]

Hi Adrian, good to hear

Here's the filter for the general CLE Blockers/Unresolved
https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=13113


Not all of these affect 2.9, so these lists may be slightly longer. However
because jira isn't routinely curated, many of the fix and affects versions
aren't always correct, especially for unresolved issues. This hopefully
will improve when the CLECC starts up in a few weeks.

Sam and I were talking and believe that to get the 2.9 release out,
*minimally* we should have
1) No unresolved 'non-security' (regular) blockers which affect 2.9
2) No unresolved security blockers/criticals which affect 2.9
3) No outstanding merges

This also doesn't necessarily mean *fixing* everything. It does at least
mean looking at every issue that currently meets these criteria,
determining if it affects 2.9, if the priority is appropriate, and for
branch managers if it is a candidate for merging. Some of the blockers are
just quick cleanup/documentation. Some of them are pretty involved.

I know Michigan (specifically Chris Kretler) has been working at times with
load testing and it's certainly something we could use more of in the
community versions of the code. I'm not sure if any of his code would be
useful to your efforts or not.

Also, If you can somehow shift an hour from your Friday occasionally to
attend the 2PM GMT release meeting it could be occasionally helpful.

On Fri, Jul 13, 2012 at 10:03 AM, Adrian Fish <adrian.r.fish at gmail.com>wrote:

> Hi All,
>
> I'm working on Fridays henceforth for Blackboard, focusing primarily on
> fixing 2.9 blockers. I'll be prioritising stuff I'm already involved with
> as I can obviously sort those out quicker but that doesn't mean I won't
> work on other stuff that's crucial to getting 2.9 out of the door. Any
> suggestions welcome.
>
> In the background of all that Chuck's asked me, on behalf of Blackboard to
> look into load testing the portal chat and to investigate unifying the JMS
> type frameworks in use in trunk and 2.9. By that I mean things like the
> MessageService's use of AMQ and portal chat's use of JGroups. One of the
> desirable outcomes of load testing portal chat will be a stress test of
> whatever framework is in use. I know there have been many spells of
> activity in this area so, again, any suggestions definitely welcome.
>
> I'm thinking  that maybe we can have multiple implementations of
> MessageService using differing transport frameworks so that we can them
> with Bb's beaudacious cloudy test bench.
>
> 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"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120713/10366f2b/attachment.html