I think that more specific tags are better in the long run than less specific. For instance:
Where not specified by the poster, but is obviously M1, we can apply magento-1
Where not specified by the OP, but is obviously M2, we can apply magento-2
Where it IS specified, but is not tagged, we can apply either tag as we see fit.
I will always prefer a Magento-...
Most new-to-Magento developers will be jumping into 2.x. Given the sheer amount of content to learn, I can see the use for dichotomous tagging as a way for developers to quickly recognize whether a question does or does not apply their issue (or to filter these in the first place).
I don't know that this needs to be addressed in Meta. I've tried previously to curb adding the Magento version number in titles, but that was struck down. As of now I suggest a comment is all that is needed to tag these questions. M2 is still quite new, and as of now there are only 800 active sites using it. This means we should assume that all questions are ...
Since SE supports partial HTML tags, it will try to render any HTML-like tags (e.g. XML), even if they are invalid. To prevent it from being rendered, you need to replace "<" character with <.
This has been mentioned before and a big portion of edits in the origination of this SE site was to move the mention of the Magento version to the tag.
I prefer this, honestly, because it cuts down on the visual noise of the question itself.
As far as tagging with a Magento-1 tag, I prefer this as well because it will have historical value. There should ...
I'm not sure there's a clear answer, so this is a good thing to discuss & decide as a community. In general, we may need to decide on a case-by-case basis. Here are my thoughts in no particular order:
When a question clearly speaks to multiple versions, this should be allowed.
For general M1 questions, the magento-1 seems appropriate, though TBH I'd ...
You're right that curation is what we need. Improving ambiguous tags is part of this (e.g. admin-grid vs. grid, as is the removal of worthless tags (e.g. get).
Beyond this, we can clean things up via tag synonyms.
Great, approved by 2/3 mods.
So if anybody wants to actively help out, these are the tags that I could find:
This is as simple to answer as it is disappointing for tag wiki editors:
Unlike other network sites, on this site the tag wikis don't have a history of being useful, so it's no wonder that they are not viewed more often. When did you see a link to a tag wiki as reference for more information the last time? Never? Right.
However, the tag excerpt is far more ...
actually, I dont see why questions for install/update problems should not get a magento-1 tag. "Ignoring" of such "rules" is more showing, that the rules for this tag may not match reality and should therefore changed.
I think that new questions (they all have a date) will be tagged magento-2 when it's about the new version.
Older questions (I can only repeat it, all questions have a date) won't get touched only because there is a new version. I'd say that is totally fine. So I don't see any need to tag old questions with magento-1 (168) or magento-1.9 (6,648) or legacy (...
Adding the magento-1 tag sounds great. Specially for questions that aren't too obvious.
If anyone can add a more specific version tag it should only be done when it's absolutely clear. Otherwise it has little use. Ran into the same issue as well and I think it should be discouraged.
Since the tag supee-6788 has been introduced, there are 70 questions, seraching for "supee-6788" yields 233 results. So individual patches, at least those with bc breaks or other complications could be a topic big enough to warrant its own tag.
But for previous patches there were not that many questions, even for the shoplift patch SUPEE-5344, ...
Well, I don't think it's a new problem, it has always been like this, it's just that now that Magento 2 becomes bigger and more people use it, the differences between M1 and M2 raised that specific problem.
What I tend to do for questions that do not require loads of code to be answered, is to post solutions for both M1 and M2, this way you ensure the ...
I've done my share on a few tags. I have also removed the tags from closed questions because if you are tagging your question and type "magento2-" you still see them appearing in the suggestions with a >0 count.
Only magento2-dev-beta is still left with a large number of questions.
magento2-pre-alpha > 0 questions
magento2-alpha > 0 questions
I don't know the related edits, but ...
if the question had no version tag
is definitly related to M1 only (screenshots, code)
is not tagged with another magento-1.x tag
... it is absolutly correct. (IMHO)
Very Good concern. You are a effective questioner.
Regarding this important topic,
I would recommend to the asker to
pick/write a tag (namely magento-1.9 or magento2 etc) on Tags line under the questioning field before clicking on Post Your Question.
To pick the Magento version tag, the asker can easily choose his/her magento version from ajaxified list ...
Nice initiative Fabian!
I'll join you. Although I haven't got enough rep in almost all of the tags to propose tag synonyms or vote for them... I did come across a lot of duplicate tags (htaccess/.htaccess, ce-188.8.131.52/magento-184.108.40.206), overly specific tags or too generic tags. Therefor I do want to join this discussion. And by "a new section next to voting, ...
If they have multiple 1.x versions inside the tags, I am for keeping the newest version, and removing the others.
Maybe also keep the lowest, when the question may include Backwards compatibility.
For example some people may ignore questions, which dont target at least 1.8, while others have more experience with problems regarding older versions.