Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Message-ID: <5A2C8481.9080101@zeus.net.au>
Date: Sun, 10 Dec 2017 10:49:05 +1000
From: Peter <jini@zeus.net.au>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20
MIME-Version: 1.0
To: dev@river.apache.org
Subject: Re: [Report] Apache River - Draft
References: <1512106999.11806.ezmlm@river.apache.org> <B1444A1B-97E6-437B-9B90-33C486727082@gmail.com> <CAK_o9cG3ez912RPctNtbYs4HoGLZHwA4yNSL_T3+-rCKN4vKkQ@mail.gmail.com>
In-Reply-To: <CAK_o9cG3ez912RPctNtbYs4HoGLZHwA4yNSL_T3+-rCKN4vKkQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Sun, 10 Dec 2017 00:49:26 -0000

+1 Peter.

On 2/12/2017 9:37 AM, Bryan Thompson wrote:
> +1
> Bryan
>
> On Dec 1, 2017 13:46, "Dan Rollo"<danrollo@gmail.com>  wrote:
>
>> +1
>>
>> -Dan
>>
>>> From: Peter<jini@zeus.net.au>
>>> Subject: [Report] Apache River - Draft
>>> Date: December 1, 2017 at 12:42:51 AM EST
>>> To: "<dev@river.apache.org>"<dev@river.apache.org>
>>>
>>>
>>> Hi River folks,
>>>
>>> Draft board report for November, postponed until December.
>>>
>>> Regards,
>>>
>>> Peter.
>>>
>>> <===========================================================>
>>>
>>> ## Description:
>>>
>>> - Apache River provides a platform for dynamic discovery and lookup
>> search of network services.  Services may be implemented in a number of
>> languages, while clients are required to be jvm based, to allow proxy jvm
>> byte code to be provisioned dynamically.
>>> ## Issues:
>>>
>>> No significant issues requiring board attention at this time.
>>>
>>> ## Activity:
>>>
>>> Minimal activity at present.
>>>
>>> - Planned relase map:
>>>
>>> Release roadmap:
>>>> River 3.0.1 - thread leak fix
>>>> River 3.1 - Modular build restructure (&   binary release)
>>>> River 3.2 - Input validation 4 Serialization, delayed unmarshalling&
>> safe ServiceRegistrar  lookup service.
>>>> River 3.3 - OSGi support
>>> ## Health report:
>>>
>>> - Minimal activity at present on dev.
>>> - No recent commit activity, but there are plans for more work in near
>> future.
>>> - Future Direction:
>>>
>>>    * Target IOT space with support for OSGi and IPv6 (security fixes
>> required prior to announcement)
>>>    * Input validation for java deserialization - prevents DOS and
>>>      Gadget attacks.
>>>    * IPv6 Multicast Service Discovery (River currently only support
>>>      IPv4 multicast discovery).
>>>    * Delayed unmarshalling for Service Lookup and Discovery (includes
>>>      SafeServiceRegistrar mentioned in release roadmap), so
>>>      authentication can occur prior to downloading service proxy's,
>>>      this addresses a long standing security issue with service lookup
>>>      while significantly improving performance under some use cases.
>>>    * Security fixes for SSL endpoints, updated to TLS v1.2 with removal
>>>      of support for insecure cyphers.
>>>    * Maven build to replace existing ant built that uses
>>>      classdepandjar, a bytecode dependency analysis build tool.
>>>
>>> ## PMC changes:
>>>
>>> - Currently 12 PMC members.
>>> - One new PMC members added in the last 3 months
>>> - Last PMC addition was Dan Rollo on Fri 1st December 2017
>>>
>>> ## Committer base changes:
>>>
>>> - Currently 16 committers.
>>>
>>> ## Releases:
>>>
>>> - River-3.0.0 was released on Wed Oct 05 2016
>>>
>>> ## Mailing list activity:
>>>
>>> - Relatively quiet in comparison to recent months, however this appears
>> as a result of reaching concensus after a period of discussion.
>>> ## JIRA activity:
>>>
>>> - Nil Activity this period.
>>>
>>>
>>>
>>>
>>>
>>