Bug#1107236: tracker.debian.org: stop showing unmaintained bullseye-backports

[Alexander Wirt <formorer@debian.org>]

Am Wed, Jun 04, 2025 at 10:35:51PM +0200 schrieb Micha Lenk:
> Hi Raphael,
> 
> I'm responding here as member of the backports team -- at least as good as I
> can.
> 
> On 03.06.25 15:05, Raphael Hertzog wrote:
> > On Tue, 03 Jun 2025, Simon McVittie wrote:
> > > As announced in
> > > https://lists.debian.org/debian-backports-announce/2024/07/msg00000.html,
> > > bullseye-backports no longer accepts uploads and should not be expected to
> > > be up-to-date with bookworm{,-security}. I think it would make sense to
> > > drop it from the "versions" and "versioned links" panels on the package
> > > tracker at this point.
> > 
> > Why?
> 
> Fair question, and to be honest I don't have an answer to that. This
> decision predates my deeper involvement in maintaining the backports
> archive. But maybe the other backports-team members can chime in here.
> 
> One potential rationale that comes to my mind is: We might want to reduce
> incentives for users of oldstable to stay on oldstable instead of updating
> to stable. Also, we might want contributors to focus on the next release
> instead of focusing on past releases, because given a limited amount of
> resources every hour spent on past release is not spent on the next release.
> Please note, this potential rationale is not necessarily my own view -- it's
> rather some random speculation.
> 
> @formorer, would you mind to share your view on this topic?

Sure, the thing is simple. We asked around the time when LTS came up if people
want to maintain backports for over the LTS lifetime.  Consensus was that most
of the maintainers don't want to do that. 

Alex