Re: Bug#747697: [RFR] templates://debian-security-support/{debian-security-support.templates}
Christoph Biedl wrote:
> Justin B Rye wrote...
>> Talking about "the regular security maintenance life cycle" worked in
>> the templates, but here it's not clear what "life cycle" you're
>> talking about - it might be the "software life cycle" (from
>> proof-of-concept to mature project to death-by-bitrot) of the
>> packages. And besides, once we start setting things up to allow an
>> oldstable-LTS with incomplete security coverage, surely that *is* the
>> planned security maintenance life cycle?
>
> This *is* mostly about squeeze-lts actually. So for that one, the life
> cycle will end in spring 2016. Should we add the "Debian" word to "the
> regular security maintenance life cycle" to clarify?
The trouble is, once this package becomes part of the standard
security support system, the claim that "maintaining security support
is not feasible for the planned life cycle" becomes confusing. Does
that mean even after taking this package into account?
Also, this use of "life cycle" to mean "support period" strikes me as
an unhelpful piece of IT industry jargon. Saying that Windows XP has
a ten year "life cycle" ought to imply that homes and businesses would
be full of baby Windows XPs just now...
Still, I don't know why I'm still talking about this when your amended
version of my patch with restored Debian branding looks okay.
[...]
> Upstream has no control here. It's the Debian security team who
> decides to end support, but of course upstream's moves have some
> influence on that. If such a decision is made, the team will also
> release a new version of debian-security-support with an updated
> list.
The part that still hasn't been made absolutely explicit is: is there
a security announcement for it, and does the new version of d-s-s go
into security.debian.org? That would make sense, but if so you'd need
to update "https://www.debian.org/security/faq#policy";...
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Reply to: