I'm getting sick of version numbers in tag names (aka version tags).
I just want them all to be just jsf. They are all about JSF. I browse and answer questions about JSF. I don't want to browse in all those different tags. I don't want gold badges for both jsf and jsf-2. I can't hammer a duplicate jsf-2.3 question because I don't have a gold badge for that.
Across years I observed that a version tag is usually only picked by the asker when a "relatively new" or "relatively old" version is being treated in the question. When the "currently mainstream" version is being treated, or when the asker is "more proficient" in the language, then askers often just pick the versionless jsf. While moving in time, this may cause confusion by future readers when the version isn't explicitly specified anywhere in the question. I try to maintain them by adding/removing the version tag depending on its relevance, and by adding the versionless tag when it's absent. It only feels a neverending story. I'm sure other tag caretakers also have mixed feelings on this.
I propose to normalize the version from the tag name:
- Ban version numbers in tag names in the model (not in the UI).
- Add an optional single-choice
versionfield to the
Tagentity in the model.
- Users with edit privileges (no suggested edits please) must be able to change versions. Users with gold tagbadges must be able to add and edit versions. I'd imagine the version edit thing to be reachable via that tag info popover (when you hover the tag). Tags themselves however should look exactly the same, the version just separated with e.g. a hyphen from the tag name.
When in place, migration of existing version tags should be piece of cake. There's apparently already a script in place which recognizes version tags, it could be reused to re-match current tags and extract the version from it into the new
The alternative would be to automatically add the versionless tag when a version tag is being used. But this is IMO only tag pollution.
I'm posting this on meta.se instead of meta.so because version numbers aren't only on SO a problem, but on basically all HW/SW related sites.