I would have sworn that we had consensus six months ago to merge Peter’s work from the qa_refactor branch back onto the trunk. Peter needs to declare it “done”, and other people need to look at it, then someone needs to release it.
Unfortunately I don’t have the spare cycles to act as release manager for that, although I’m happy to offer advice on how to get the artifacts into Maven Central, etc. Cheers, Greg Trasuk. On Apr 30, 2015, at 11:13 AM, Dennis Reedy <dennis.re...@gmail.com> wrote: > Hi, > > I didn’t want to add this to the thread that Patricia started, but IMO I’d > like us to push for a new release ASAP. Peter’s done a ton of work, there are > improvements needed to the RMI classloading approach that can help projects > out there today that use OSGi, and we have to do something. > > What I’d like to suggest is we create version 3.0, rename the com.sun.jini > namespace to org.apache.river, and produce a new release. Lets get this done > over the next quarter. I know there are alot of details with this proposal, > and esoteric discussions surrounding “what are we”, but we either release or > die. IMO, its that simple. > > If anyone does not like whats in 3.0, they can still use 2.2.2. If bug fixes > are needed for 2.2.2 we can still provide support for it. Release early, > release often. > > Regards > > Dennis
