> i like major.minor.patch +1 For most packages, I tend to avoid x.x.0 and wait for x.x.1 or x.x.2 before upgrading. (And if it's an Atlassian product, I tend to wait for x.x.4)
> i like neat codebases, so the "deprecate in A, leave in B, remove in > C" sounds good to me. I'm not sure I understand correctly ... do they literally use A B & C versions, or do you mean "deprecate in 1.0, leave in 1.1, remove in 1.2" or "deprecate in 1.x, leave in 2.x, remove in 3.x" ? > as for "forcing people to rewrite", i don't think anyone is forcing > them to use a new version. if they don't want to rewrite and their > app is stable with an older version, they should not upgrade and risk > instability. +1 If it ain't broke, and I don't need the new features, and there isn't a "critical" fix/update/improvement in the old lib then it may stay at 1.x forever. ;-) -Timo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
