. > > For the rare edge case where we have to stop supporting something entirely > because it's incompatible with a JDK release (has this happened more than > the 1 time?) - I think a reasonable fallback is to just not backport new > JDK support and consider carrying forward the older JDK support until the > release w/the feature in it is EoL'ed. That'd allow us to continue to run > in-jvm upgrade dtests between the versions on the older JDK. >
This. I think the idea of adding new major JDKs to release branches for a number of reasons, in theory at least. In practice I think this would have to be discussed and evaluated for each new JDK and release branch. And this would mean we can drop a JDK in trunk once it's no longer the latest in all latest maintained patch versions.
