+1. I think in my horizon, users have (by now) migrated to Java 8 (if for nothing else, for security updates). -Marshall
On 11/6/2018 5:42 PM, Richard Eckart de Castilho wrote: > I believe the type of communities I'm mostly dealing with wouldn't have a > problem > with the change. Within your horizon, you probably have more users on legacy > systems. > So if you also believe the effect is negligible, so be it. If we are wrong, > we can > always do a 2.10.4 back with Java 7 compatibility level. > > -- Richard > > P.S.: So... does that mean we can now start using Java 8 language features in > v2 code? :) > >> On 6. Nov 2018, at 22:51, Marshall Schor <[email protected]> wrote: >> >> I'm not sure anything really requires Java 8. I could probably easily put it >> back to Java 7. I think I bumped it up when I was trying to get things to >> build >> under Java 11. >> >> I guess I just thought that by now, no one will be using Java 7, since it's >> been >> out of maintenance for a while. (Oracle ceased public availability of >> security >> fixes and upgrades for Java 7 as of April 2015). >> >> Because of this, I thought that it would not be a major change for most >> users - >> I think they wouldn't notice; so in practical terms, an unnoticed change >> might >> not warrant a bump to 2.11 :-). >> >> If you feel strongly, I'll redo the release without changing the target to >> java >> 8 (leaving it at 7), but I think it would be work for no real-world benefit. >> >> -Marshall >
