For example, datetime and datetime2 -- should they really be separate tags?
Yes, they should: datetime
has been declare obsolete and not any more maintained. It is still in the distributions for allowing compilation of older documents without needing to change them.
The new package datetime2
is different and incompatible with its predecessor, so questions dealing with it should not be confused with those referring to the obsolete version.
-
The intent of the question was more of the general case, but I think that the 'incompatible changes' argument applies to most – if not all – sequels. Would you agree? – Sean Allred Apr 18 '15 at 0:21
In general, if the entity they represent is considered different, then separate tags would be okay. However, never use version-related tags, as versions become outdated and therefore typically useless.
For example, while we do have a texlive2010 tag, it was has been voted as a synonym for texlive, and rightly so. There would be little value in having a tag for each version of TeX Live. In the same way, version-specific tags for packages (or software) would not be very helpful.
Reference: What are the guidelines for using version-specific tags?
-
If separate tags are OK, but versions should not be used to differentiate them, what should be used to make them unique? – Paul Gessler Apr 18 '15 at 2:23
-
@PaulGessler: Well in this case, the two packages are named similarly but are different. I would think it best to stick to datetime and datetime2. You'd probably find similar likeness between algorithms, algorithm2e, algorithmicx... – Werner Apr 18 '15 at 5:46
tlmgr
, I guess. – egreg Apr 17 '15 at 23:49:)
– Paulo Cereda Apr 18 '15 at 12:00