+1. to release early, release often. Go for v3, seems simplest. If someone really wants fixes in 2.x, then you release from the branch.
Gary On Fri, Dec 2, 2011 at 12:27 PM, henrib <hen...@apache.org> wrote: > I've done the same thing and been pushing JEXL snapshots for sometime to > avoid the unpleasant moment, so unpleasant that I've procrastinated enough > to now have to consider alternatives. > I find disturbing that committers fear to release and that goodwill to > share > features and code is killed by the process that should help publish them - > not oppose them! > > I agree that a "release early, release often" scheme would help but I've no > idea how to achieve this without a "release faster" mean. > > However, I ultimately suspect that the vested interest of some in promoting > a hard, difficult and lengthy process relates to how their bills get payed > and by whom; there is a huge difference in those of us doing this as a > "goodwill hobby" - so to speak - because we feel it is good ethics to > contribute back and those who make a living from it. Can't blame them for > making sure their fees stay high by ensuring "hobbyists" don't get too > efficient! (just kidding :-)) > > Cheers, > Henrib > > -- > View this message in context: > http://apache-commons.680414.n4.nabble.com/JEXL-Jexl-2-1-tp4147180p4148135.html > Sent from the Commons - Dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
