On Thu, Jul 31, 2014 at 8:29 AM, G. Matthew Rice <[email protected]> wrote:
> Perhaps, we could get the LPI marketing department to try a survey
> along the lines of "what's the oldest version of a distro that you
> still have to support?" :)
>
βI've stated what I feel is a good "general rule" βon this in the past.
Using Red Hat [1] and SuSE [2] Lifecycles, which are the longest-term
support lifecycles, technologies in these Enterprise distros that are ...
- Phase/Production 1 (under 5-6 years):
Actively supported, enhanced
-> should be covered in objectives
- Phase/Production 3 (over 7-8 years):
Pure maintenance
-> If not in next version,
should be dropped from objectives
Which means, basically ...
- Phase/Production 2 (around 6-7 years):
Entering maintenance-only
-> Check next version (should be out),
if not in next version,
should be dropped from objectives
if in next version,
still as "Phase/Production 1"
It's really this simple ...
We look at RHEL and SLES distros that are under 6 years old, and see if a
technology is in use. If not, drop it from the next set of objectives.
In fact, by the time any RHEL or SLES distro is 6-7 years old, the next
version should already be out, so it can be checked if the technology is
still supported. If not, it should be dropped from the next set of
objectives.
Which means by the time any RHEL or SLES distro with the technology is 7-8+
years old, and a newer does not have it, it should _already_ be dropped
from any "new revision" of the distribution.
Because if it's that old, no other distro is honestly likely to have it
either, even if they adopted it later.
Most "qualitative" answer I can give, with a very, very "objective"
baseline. Sure, there might be a few exceptions here and there, but they
should be _rare_.
-- bjs
[1] https://access.redhat.com/support/policy/updates/errata
[2] https://www.suse.com/support/policy.html
ββ
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
