I've seen this question - What are the guidelines for using version-specific tags? - But it doesn't address whether synonyms should be created or not. The accepted answer just says that version-specific tags should be avoided unless it is an essential part of the question.
I am having trouble deciding if I should propose tag synonyms, particularly for version-specific TeamCity tags.
The purpose of tag synonyms (according to the privileges page) seems to be:
What are tag synonyms?
Tag synonyms allow us to fix incorrect tags by substituting them with the correct tags.
While I wouldn't say that version-specific tags are always incorrect, I think they'd often be misused, and should always be paired with the "master" tag. This is why a tag synonym makes sense to me. But maybe I am misunderstanding the point of tag synonyms. Are they just to correct things like typos (
modeling), or give a more canonical name to things (
Person producing tags:
- .Net 4.0 was just released (or just put in beta). I have a problem with a .Net 4.0 feature,
- I made a single change in a check in, upgrading my project to target .Net 4.0. It still compiles, but it fails to run on client machines. Similar upgrades went right, so this must be a 4.0 specific problem.
- I am writing a program and I happen to be targeting .Net 4.0. I may or may not be using 4.0 specific features. Heck, I might only be using 2.0-specific features.
Person consuming tags:
- I am interested in features new to .Net 4.0. Or, 2.0 is ancient news so I don't really want questions that target those features.
- I have a problem that is 4.0 framework specific, and I'm about to ask a question. I'm searching to see if someone already has my problem, so I filter based on tag.
- I want to watch and answer .Net questions because I have an expertise in them.
All of these have two sides to them that may or may not be impacted if version-specific tags are removed, or questions are inappropriately tagged.
I am having a hard time seeing how these are addressed by the tag synonym feature, and which are supposed to be addressed by it. Maybe that means version specific tags should stay non-synonyms, and the tags' usages should be corrected when necessary?