river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Hobbs <tvho...@googlemail.com>
Subject Re: [DRAFT][REPORT] River Board Report April 2011
Date Mon, 11 Apr 2011 07:45:29 GMT
Okay, will remove the alarm bells bit.  I wasn't have a dig at anyone with
it, just remarking on the number of messages sent to dev@ and commits - as
much my own activity as anyone else's.

There's a lot of interesting papers around about distributed state and fault
tolerance, isn't there?  it almost makes me wish I commuted to work on a
train to give me more time to read them... but only almost, I hate trains!

On 11 Apr 2011 00:14, "Patricia Shanahan" <pats@acm.org> wrote:
> Although I'm taking time out to deal with the RIVER-395 patch, my main
> River activity is educating myself about fault tolerant transactions, by
> reading papers on the subject. That does not produce much in the way of
> immediately visible results, but may be very useful in the long term.
> Patricia
> On 4/10/2011 3:52 PM, Peter Firmstone wrote:
>> Good job Tom, I wouldn't worry about the alarm bells bit, I think people
>> are still active behind the scenes, or thinking about what needs to
>> happen next. I'll get back into it soon too.
>> Cheers,
>> Peter.
>> Tom Hobbs wrote:
>>> Comments always welcome, due date is 18th March.
>>> Below is the April board report for River
>>> Apache River is a distributed computing architecture, based on the JSK
>>> Starter Kit Source code donated by Sun Microsystems, for the Jini
>>> Specification.
>>> Releases:
>>> First TLP release still hasn't been cut. This is due to a user
>>> raising concerns about a newly discovered (or introduced?) bug with a
>>> specific JDK on a specific OS.
>>> Progress:
>>> There has been some discussion on dev@. There has been a marked drop
>>> in the number of participants and areas of discussion though. Some
>>> progress has been made researching one or two areas of specific
>>> interest regarding new River features. This will be the last of our
>>> monthly reports, we expect to change to quarterly reports from now on.
>>> Community:
>>> As above, community activity has dropped, but given the relative small
>>> size of it one or two members being not participating for myriad
>>> reasons has a disproportionate effect. This is still not a concern
>>> right now, however if it continues for another couple of months then
>>> alarms bells should start to ring.
>>> Issues:
>>> No board issues at this time.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message