Ian Shields Ph.D. Linux Technologist, ISV & Developer Relations IBM Corp Research Triangle Park, NC [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote on 01/28/2008 11:02:27 AM: > Internally (and I'll make that publicly visible, too), the objectives are > versioned as major.minor where the major version increases with each > complete redo (including a JTA survey, like this time). We've committed to a > 5 year cycle on these. > > The minor version increases when there is just a interim assessment of > changes that are needed. This will happen, at least, every 2.5 years. > > So, the version for these new objectives will be 2.0. I think making that externally visible will be a huge help. I'd put the version near the top of my tutorials so folks would know exactly what level the tutorials correspond to. Right now, it's hit or miss. > > I'd like to avoid numbering the objectives as 2.0.101.1 (etc) as that looks > really icky (and looks too much like RCS/CVS branching, which also irks me). > So if someone has a cool idea, please speak up. As long as the version is painfully obvious and clearly visible, I'm not in favor of massively complex numbering. > > -- > g. matthew rice <[EMAIL PROTECTED]> starnix care, toronto, ontario, ca > phone: 647.722.5301 x242 gpg id: EF9AAD20 > http://www.starnix.com professional linux services & products
_______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
