Ciao Antonio, > How about set up a wiki page listing the goal to be achieved in order to > achieve a new release > (and maybe another one for the graduation, if not too early :S)? >
sounds the way to go, feel free to setup pages on the Amber wiki[1]! I agree as well for determining a checklist for the graduation and keep in mind 1) a stable release and 2) community development are crucial issues ATM, IMHO. If there isn't an active community contributing on the project, even if the code is mature, I'm worried it wouldn't be accepted as TLP. > +1 also for me with a little but... > I do agree with you that the 1.0(a) stuff is kind of obsolete at this point. > I would do an exception for the client part though. Namely IMHO it would be > nice to have a nice common API for the client that would work with both the > 1.0(a)/2.0 implementation. > How does it sounds? I think it would have been more sense at the early Amber days on late 2010 when we started, today implementing a deprecated protocol sounds more an academical exercise rather then providing a useful library. Please take this as a strict personal point of view ;) Other feedbacks from other committers? TIA, - Simo [1] https://cwiki.apache.org/confluence/display/AMBER/Index http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/
