I started a new thread for I was under the impression it was policy not to have discussions on a vote thread as it complicates tallying.
I agree with the recollection of John. It would be good if those with a more in depth knowledge of the rules here could explain the possibilities with regard to releasing in the com.sun.jini namespace. The comparison with Wicket came up, and although I don't think it was the intention of Gianugo to compare River with Wicket I believe Wicket is a complete different project. They did just one release after which they directly asked for graduation to TLP which only has to be formalized by the board I believe. They came in Incubator after us and are almost out of the gate, they had a diverse community to start with that only needed to sort out the legal matters and to learn "the Apache way". Although my memory is faulty and vague, I also believe they did or intended to do bug-fix releases at Codehaus while doing their work here in Incubation. It is my expectation that River will be much longer in Incubation due to the fact this was a completely Sun driven effort in terms of coding. Although estimations are hard to give I won't be surprised as it would be in line with a project such as Derby. For me moving to org.apache.river in the first releases (if these have to be soon) while having no sight of a graduation is something I consider a bridge too far. Not only do I have a lot of patches in the com.sun.jini namespace that needs to be integrated, I also have a lot of derivative work based on the com.sun.jini namespace that is in production at places and that needs ongoing support. For me switching is something I really would like to postpone until the larger outlines for this project are clear, e.g. are we going to make incompatible API changes in the com.sun.jini API, etc. Personally I have no problem with no official release in com.sun.jini and let people build one from SVN themselves [1] and postpone an official release in the org.apache.river namespace if we have some signs we are heading the right way, but I believe others do. [1] I realize this comes to the expense of user satisfaction, but I also believe this way they become a little bit more involved and get a bit more understanding of the project. As I believe incubation is also meant for building a developer community I don't consider this 'bad'. A proper explanation near the download section will do fine I guess. -- Mark
