river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benson Margulies <bimargul...@gmail.com>
Subject Re: [DRAFT] December Report
Date Mon, 06 Dec 2010 14:29:04 GMT
It's OK with mentor #2, and one mentor is enough.

I don't think that a formal vote is required.

On Mon, Dec 6, 2010 at 9:17 AM, Patricia Shanahan <pats@acm.org> wrote:
> Do we need to vote on this? If so, +1
>
> Patricia
>
>
> Tom Hobbs wrote:
>>
>> Updated the three next important steps and moved the originals in the
>> body of the report.  Added Jukka as the "signed by mentor"
>>
>>>>> On Mon, Dec 6, 2010 at 9:31 AM, Tom Hobbs <tvhobbs@googlemail.com>
>>>>> wrote:
>>>>>>
>>>>>> Here's the status report for December.
>>>>>>
>>>>>> Comments?
>>>>>>
>>>>>> River
>>>>>>
>>>>>> Apache River is a distributed computing architecture, based on the
JSK
>>>>>> Starter Kit Source code donated by Sun Microsystems, for the Jini
>>>>>> Specification. While generally referred to as a Service Architecture,
>>>>>> it might be more easily explained to those familiar with Dependency
>>>>>> Injection as a Protocol Independent, Distributed Dependency Injection
>>>>>> Architecture, suited to both hardware and software. Instead of
>>>>>> depending on Protocols directly for communication, everything is
>>>>>> abstracted behind a Java interface, allowing protocols and
>>>>>> implementations to be swapped freely, programming languages other
than
>>>>>> Java can also participate.
>>>>>>
>>>>>> The activity on the River project continues to grow and is seeing
>>>>>> renewed interest from people who had previously fallen silent.  The
>>>>>> current development team feels that we are ready to start the
>>>>>> Graduation process to a TLP.
>>>>>>
>>>>>> The next release 2.2.0 is scheduled for January, this is likely to
be
>>>>>> a bug-fix release and will hopefully be our last release before
>>>>>> graduation.
>>>>>>
>>>>>> New functionality and enhancements has currently been suspended in
>>>>>> favour of bug-fixes and the work towards graduation.  The following
>>>>>> rough road map has been provisionally agreed;
>>>>>>
>>>>>>  * Graduation as top level project river.apache.org
>>>>>>  * Rename com.sun namespace to org.apache.river
>>>>>>  * Modular build & JDK policy
>>>>>>
>>>>>> After this has been completed then the previous work on new
>>>>>> functionality and enhancements will be picked up again.  These will
>>>>>> include;
>>>>>>  * Dynamic Grants at Runtime, based on CodeSource, Code Signer
>>>>>> Certificate chains , ProtectionDomain or ClassLoader.
>>>>>>  * Dynamic Revoke of Grant's at Runtime
>>>>>>  * Securing proxy downloads and unmarshalling
>>>>>>
>>>>>> Additionally work is continuing on the build and test environments.
>>>>>>  The project has recently been able to run all the categories of
the QA
>>>>>> tests which is a significant accomplishment, but it does make for
a rather
>>>>>> long test sequence.  They have highlighted several bugs which have
been
>>>>>> fixed.  More of the JTREG tests are also passing after fixes to
the
>>>>>> environment and the tests themselves.
>>>>>>
>>>>>> The website has been moved to the new Apache CMS environment and
has
>>>>>> seen further increases in the level of documentation available,
>>>>>> particular articles which are useful to people starting to use and
>>>>>> develop River.
>>>>>>
>>>>>> 3 most important issues:
>>>>>> * List future River PMC members and select the initial PMC chair
>>>>>> * Prepare the TLP graduation resolution
>>>>>> * Vote on graduation
>>>>>>
>>>>>> Signed off by mentor:
>>>>>>
>>>>>> Jukka Zitting
>>>>
>>
>
>

Mime
View raw message