As a followup to
TL;DR -- my main point in that post:
The danger of version tags is that they become de-facto requirements -- crutches to avoid thinking about what tags are actually useful on a question. Left unchecked, version tags will poison your tagging system rendering it useless. Don't get me wrong: version tags can exist, but should only be used on posts that are truly specific to a particular version.
With that in mind, I think we have a compromise that is workable.
Henceforth, version tags for the core product discussed on a site entirely dedicated to that product will be numbers only, such as
This solves a bunch of problems:
It reduces the redundant repetition of "Sharepoint" in tags on a website that is already entirely dedicated to Sharepoint.
It avoids "autocomplete syndrome" where new users type the first thing that comes to mind in the tags field, Sharepoint, and are forced into this rigid and dangerous "oh, I must specify a version" mindset from the get-go.
When users do begin typing a number in the tags field, they will get the version, which is probably what they wanted at that point so we are guessing their intentions better.
The number tags are clean and simple; when you see 2010 on a Sharepoint site, it is IMO quite obvious what that tag is for.
Bottom line, it allows the version tags to exist -- which as I have always said is fine -- while keeping their use under control, so they can be applied only to questions that are truly version specific as originally intended.