Re: Bug#747697: [LCFC] templates://debian-security-support/{debian-security-support.templates}
Christoph Biedl wrote:
> victory wrote...
>> is "limited" used for packages which eg. has been doomed its EOL?
>> if that's it, it will better to say like "security support *period*"
>
> This is from the package description:
>
> | This package provides a program to identify installed packages for
> | which support has had to be limited or prematurely ended, and to
> | alert the administrator.
>
> If this that not provide enough information we might as well start
> from scratch.
>
> The message should be:
>
> * Some packages fell out of support entirely ("ended").
> * Other packages are supported but not to full extent ("limited").
If we need a synonym for "limited" that clearly isn't talking about
duration, we might talk about support being "reduced" or "downgraded"
or something. Or looking at the version in my last patch:
# This package provides a program to identify installed packages for
# which it has been necessary to limit or prematurely end support, and to
# alert the administrator.
It might not be necessary to change that - I would hope that in "limit
or prematurely end" it's clear that "limit" itself can't mean
"prematurely end" - but if I try to rephrase it I end up with:
This package provides a program to identify installed packages for
which it has been necessary to end or reduce security support early,
and to alert the administrator.
Is that any better?
("Early"? "Prematurely"? "Ahead of schedule"?)
Then there's that final paragraph that we still need to thrash out.
| Updated checklists are provided via regular and/or security updates.
Does "regular updates" mean "updates every n days", or "updates of the
usual kind" (which would normally mean "uploaded to unstable"), or
what exactly?
The alternative of
| Updated checklists are provided by new package versions.
is a bad idea since all packages have new versions, but the default
assumption in Debian is that they won't reach stable, and this doesn't
explicitly override that default. How about something like:
New versions updating the checklists included in the stable release
will be provided via security updates.
But it would help if we had a cover term meaning "security updates in
the strict sense, LTS updates, and whatever other kinds are
appropriate". Maybe "support updates"? "Special updates"? Maybe
even
New versions of this package with updated checklists will be provided
via standard and/or extended security support.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Reply to: