+1 to all of the below. The lesson from Lang imo is to charge in and just do it. It'll generate ideas once people are free to consider backwards incompatible changes. Rolling back is always possible if we decide we didn't really justify a 2.0.
Look at what else is out there. Is the scope of Codec correct, are there things that should be added to the scope. Is there other useful code that can be included. Hen On Tue, Mar 29, 2011 at 10:44 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > Hi All, > > Now that codec 1.5 is out, I would like thoughts on this plan for codec 2.0: > > - Create a SVN branch for 1.x > > Then in trunk: > - Correct Maven group id, which implies: > - Repackage to o.a.c.codec2 > - Use Java 5 > - Use JUnit 4 > > What else? Thoughts? > > Thank you, > Gary > -- > http://garygregory.wordpress.com/ > http://garygregory.com/ > http://people.apache.org/~ggregory/ > http://twitter.com/GaryGregory > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
