I don't think we need to keep arguing this, when we discussed this last time we said we'll do an intermediate Java 7-version - if there are too many screams (I suspect almost none) then we can be more careful before moving to Java 8 afterwards, which would give the biggest benefit (and need more help from Lang).
In a way Java 7 will mainly just give us style benefits and a couple of code simplifications, which is important to make Commons Lang's code more inviting for new contributors. On 24 October 2016 at 14:41, Matt Sicker <boa...@gmail.com> wrote: > 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> -- Stian Soiland-Reyes http://orcid.org/0000-0001-9842-9718 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
