David, first: thanks for heading to meta to ask this questions! I'd like to think I sort of helped prompt it since I rejected some of your tag edits. Sorry! :/
I think that we really need to settle on tags used to indicate versions, and then migrate the deemed old tags as appropriate. I'm not sure if there is a way for anyone (maybe mod only) to retag all questions from one to another, but there is a way to mark a tag as an alias of another.
As they are relevant, here are two links to meta questions where version tags came up fairly early on:
Something pointed out by Tim in a comment on the 2nd post…
If you specify a ce-1.3 tag people will ask you for a clarification. because different versions of 1.3.x.x (and 1.4.x.x also) have significant changes.
In comments on an answer further down the same page…
People obsess with all the dots because the bruhaha around 1.4.2 or 1.4.3 or whatever it was when the magento-verse passed too close to a dwarf star and altered course forever. 1.7 is 1.7 and that's about all that's needed since 1.5. A better tag would be to highlight BIG and dangerous changes between versions; major or minor
I will point out a few things:
- There are major differences between EE 126.96.36.199 and EE 188.8.131.52 in the Mage_PayPal module. We (re)discovered this when we recently launched our PayPal providing saved credit card functionality atop the original integration. It made a big difference because the config system for the base totally changed (and to top things off you can't specify minor release in EE compatibility on Connect) — The same (I believe) goes for CE 184.108.40.206 as compared to CE 220.127.116.11
- We all know that CE 1.8 was just released, and with the release some stuff included in the alpha was removed due to issues which have been being ironed out in the EE 1.13 core as it's been deployed into production environments. This is all fine and dandy, until these changes pulled from the initial 1.8 release are henceforth included in the CE 18.104.22.168 release as I expect them to be.
Both of the above are examples of continued usefulness of having the full version number be used in tags. Once 1.8.1 is released (and assuming the plans don't change) I would expect questions will start being asked about URL key related changes…and if you specify only 1.8 it will not be clear to readers which version the OP is using or asking about, but will make a difference as far as the solution goes.
I am personally fine with longer tags like "magento-1.x" but also see the merit of using shorter tags which include the full version. Or more correctly stated, I see including the full version number as necessary. Maybe we should try and encourage including both a generic major release number tag as well as a minor release version tag.
For now though, the "magento-1.x" tags have had their descriptions changed (for quite a while now) to read something like this:
This tag is redundant and shall not be used. Please use ce-1.7.x.x tag instead.
If we decide to "reopen" the magento-1.x" tags for use, then I'm totally fine with it. However, if a user tags a question with a specific version number, I would much prefer to see the generic tag added as opposed to replace the original and more specific tag.
To answer the question about whether or not there are methods to migrate tags: I believe there are ways as I see evidence of such on the tag synonyms page, but I'm not sure all users can do so. But, all users can suggest synonyms for tags here: https://magento.stackexchange.com/tags/synonyms