-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Just my $0.02:
A certification program such as LPI's is essentially a skills standard, and as such we have a responsibility to move slowly and cautiously on what is included in this standard.
IMO it's more important that we follow the Linux Standard Base spec than the release schedules of any specific tool(s) or even the kernel. We can easily drive ourselves crazy following the progress of every component of Linux distributions -- following the LSB offers a software target for us that is both more stable and easier to follow (because it moves more slowly).
It is necessary for the community, from candidates to courseware authors to HR personnel, that our skills target does not move very quickly or abruptly. It's also important to LPI's neutrality that we endorse skills on software that is to be found on most distributions, not only the distributions that are quickest to implement new tool releases.
If anything, we need to be vigilant that the LPI program matches LSB-mandated tools and versions. When LSB publishes release 2.0 -- now in a late beta version -- LPI should determine any changes involved in having the LPIC program match the revised LSB standards. Even so, we need to produce a roadmap for the community that details the speed at which we would implement such changes.
- - Evan
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBDVHPEaxkgziIBO8RAsoZAJ9fenobgbuw6TAuaATp7M1qJWPdGACg3WTM bQDBFsuQV/k/7JPo0ZPx/oE= =MzM9 -----END PGP SIGNATURE-----
_______________________________________________ lpi-examdev mailing list [EMAIL PROTECTED] http://list.lpi.org/mailman/listinfo/lpi-examdev
