Thanks Bryan,
Be good to have a release to address the memory bug (no pun intended).
Even better will be future binary releases based on Modules. Services
built with modules are so much simpler. But so no one gets upset, all
existing build tools, systems and conventions will continue to work too.
Cheers,
Peter.
On 12/09/2017 6:55 AM, Bryan Thompson wrote:
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<j...@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.
