Re: Bug#975016: OpenJDK 15 support state for Bullseye
On Thu, Nov 19, 2020 at 07:47:14PM +0100, Moritz Mühlenhoff wrote:
> On Wed, Nov 18, 2020 at 10:31:30PM +0100, Thorsten Glaser wrote:
> > I think nobody wants to switch default-jdk to 17 or even not ship
> > 11 at all any more or stop supporting it during bullseye’s lifetime.
> > Maybe that also was too implicit?
> Exactly, the supported Java release for the entire Bullseye lifetime will
> be 11 (which packages will build-depend on and what's provided by
> The idea is to include 15/16 so that later on when 17 is ready, 17
> can be made available in addition via backports (since at some point
> later in the bullseye lifecycle might be software one wants to run
> which requires 17 as the next LTS.
17 can be in unstable before the release of bullseye.
If this is then eligible for testing migration except for the freeze,
it would enter testing in the first migration after the release.
With slight bending of the rules someone with ftp powers could then
copy the sources+binaries from bookworm/testing to bullseye-backports.
Slightly less bending of the rules and only marginally more effort would
be to build ~bpo11+1 binaries for all bullseye release architectures
in unstable before the release of bullseye.
Either option sounds better to me than shipping 15 or 16 in a stable
release solely for bootstrapping 17 in backports.