You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Peter Firmstone <ji...@zeus.net.au> on 2011/02/12 02:36:46 UTC

Future Roadmap WAS: Re: [VOTE] [TALLY] drop jdk 1.4 compatibility

Sim IJskes - QCG wrote:
> Sim IJskes +1
> Jeff Ramsdale +1 (non-binding)
> Patricia Shanahan +1
> jgrahn@simulexinc.com +1 (non-binding)
> Dan Creswell +1 (non-binding)
> Tom Hobbs +1
> Peter Firmstone +1
> Dennis Reedy +1 (non-binding)
> Greg Trasuk +1
>
> Gr. Sim
>
>

We need to update our future roadmap on the website, it currently reads:

Future Roadmap:

    * Integrate Jini Surrogate Architecture.
    * Apache River - Java CDC support for dynamic code downloading and
      Jini Services utilising a subset of Jini's API.
    * Apache River 2.2.0 Release, Scheduled for December.
    * Better "Getting starting" documentation for new River developers
    * Better resources for users of River (Thanks to Tim Blackman for
      /Jini-in-a-Jar/ donation)

Java CDC support is no longer possible with future releases, it needs to 
be removed.

The River 2.2.0 release missed December, what's currently in trunk is 
not ready for release:

What we need to do for release:

    * Integrate Patricia's fixes to Outrigger
    * Look at the two failing java 1.6 tests on Solaris sparc, fixing
      these tests might fix a bug that is present on all platforms, but
      not currently experiencing test failures.  Long term, I don't see
      much future for sparc unfortunately.  Yes it is a more secure and
      reliable architecture (relative to x86), but Solaris is expensive
      to support & OpenSolaris appears to have been effectively killed.
    * Decide where the new velocity configuration fits in (Thanks Sim
      for the contribution), should this be a Service Provider Interface
      like Groovy config?  Or should we have a new builder similar to
      that provided for velocity suitable for all configuration types? 
      I'm assuming there is a reason that a builder has been used, sorry
      I'm not familiar with velocity, but this might make deployment
      easier for those who are.


We also need to consider where we want to go with River, what else 
should be in our Future Roadmap?

Regards,

Peter.