Keeping open a maintenance branch for 3.5 sounds like a good idea. If it really does end up taking over a year before a 3.6 release needs to be made, then Java 6 may be a moot point by then. Either way, it sounds like migrating to Java 7 for a 3.6 release isn't a bad idea unless it turns out there are no useful API additions that can be made without jumping to Java 8.
On 24 October 2016 at 08:35, Emmanuel Bourg <ebo...@apache.org> wrote: > Le 23/10/2016 à 09:30, Gary Gregory a écrit : > > > Thoughts? > > If this means doing only trivial internal code changes with no benefit > to the end users then I don't think it's worth it. I would either stick > to Java 6 or go to Java 8 and offer some real new stuff. > > Emmanuel Bourg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- Matt Sicker <boa...@gmail.com>
