Hi, I thought we had a policy to keep BC for minor releases?
I understand that the removed methods are not in core classes but it still breaks BC. Are sure we want that? Are the removed methods confusing in a way that can be construed as keeping them being a bug? Gary On Mon, Nov 26, 2012 at 1:29 PM, sebb <seb...@gmail.com> wrote: > This is a vote to release Apache Commons NET 3.2 based on RC1. > > [ ] +1 release it > [ ] +0 go ahead I don't care > [ ] -1 no, do not release it because... > > tag: > https://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_2_RC1/(r1413727) > > site: > http://people.apache.org/~sebb/net-3.2-RC1/ > > The Javadocs (1.4.1) link does not work, nor does the download link. > These will be OK once the site is deployed. > > Source and binary archives (tar.gz and .zip) and Maven jars: > https://repository.apache.org/content/repositories/orgapachecommons-078/ > > [The tar.gz and .zip files will be moved to dist/commons/net before > promoting the Maven jars to release status] > > Vote will remain open for at least 72 hours. > > --------------------------------------------------------------------- > 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
