For what it is worth, I very much agree with Marting and Adrian. It would make matters easier for downstream consumers if we could at least retain N-2 compatibility, if compatibility to LTS is too much of a hassle for Oracle.
Best Regards, Thomas On Wed, Mar 21, 2018 at 11:41 PM, John Paul Adrian Glaubitz < glaub...@physik.fu-berlin.de> wrote: > On 03/22/2018 07:07 AM, Martin Buchholz wrote: > > But for users, being able to bootstrap with an ancient jdk is definitely > > convenient. > > Convenient is an understatement. Always enforcing the N-1 version to be > used can be quite painful for downstream distributions. Rust upstream > does the same thing and it becomes very frustrating when bootstrapping > the compiler. > > When, for example, an architecture has fallen back a couple of releases > of OpenJDK, I would have to go through the whole chain of 8->9->10->11 > to get the latest OpenJDK. I know that cross-compiling is possible, but > it's not always the easiest option. > > So, from a downstream perspective, allowing the oldest possible version > is always a desirable feature to have. I do understand it though when > OpenJDK 11 requires features from OpenJDK 10 which would rule out older > versions completely. > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 >
