sebb wrote: > On 20 December 2011 14:07, Gary Gregory <garydgreg...@gmail.com> wrote:
[snip] > That would be contrary to the Commons versioning rules - a package > name change requires a major version bump. > >> For 1.0, we should make all big changes before 1.0, which may feel >> like a big bang release. Anything that breaks compatibility should be >> done now before a 1.0. > > Agreed. > >> Using java 5 can break source compat once add generics, so you only >> want to do that when you have to. If the java 5 changes are not user >> visible like using enhanced for loops the you can do it anytime. > > Someone else suggested updating source and target version to 1.5, but > not adding generics. > I think the idea was to allow Java 5 methods such as StringBuilder etc. [snip] Remember that this also allow the usage of javax.imageio which provides some more efficient ways to deal with IO for image data. > However AFAIK this will result in huge numbers of compiler warnings. > Since Apache releases source, IMO we should at least ensure that the > source compiles cleanly. > > So I am -1 on changing the source requirements without fixing generics. > >> But, if someone wants to put the time in now, go for it! :) > >> Performance improvements can come in after for example but I'll let >> someone else make that call. >> >> Now is the time to get the API right. > > Indeed. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
