Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
MIME-Version: 1.0
Sender: bryan@systap.com
In-Reply-To: <59438BF1.5030109@zeus.net.au>
References: <59438BF1.5030109@zeus.net.au>
From: Bryan Thompson <bryan@blazegraph.com>
Date: Mon, 11 Sep 2017 13:55:34 -0700
Message-ID: <CAK_o9cG_-uLLGx9SNPrWz3ZvsNWgiDZrpx5SCWZUNGNUpy4Nhg@mail.gmail.com>
Subject: Re: Participation
To: "<dev@river.apache.org>" <dev@river.apache.org>
Content-Type: text/plain; charset="UTF-8"
archived-at: Mon, 11 Sep 2017 21:01:10 -0000

Peter,

Just reviewed the release.  My apologies for taking so long to get
this done.  It's been a busy time.  Thanks for all the effort to pull
this together.

Bryan

On Fri, Jun 16, 2017 at 12:42 AM, Peter <jini@zeus.net.au> wrote:
> Anyone have some cycles to participate in the release vetting process?
>
> River 3.0.1 is a bug fix release.
>
> Remember if we're unable to continue this project, then we lose the ability
> to maintain River / Jini and we also lose the legal protections and
> visibility of Apache.
>
> Apart from modularity (which lowers technical barriers to entry) and
> improved security, I think the most important upcoming feature is IPv6
> support, it would be ironic to see River fall over before IPv6 becomes
> ubiquitous, given that the deficiencies of IPv4 is likely responsible for
> Jini's failure to gain widespread adoption.
>
> Note also that in spite of "new features" River remains backward compatible
> (in the net.jini.* namespace) with earlier releases.  I'm also working on a
> compatibility layer for easier migration away from com.sun.jini to
> org.apache.river namespaces.
>
> We can't do it by ourselves, we need you too.
>
> Regards,
>
> Peter.
>
>