Drupal Version Tags (= DVT ) are the tags such as 6, 7, 8. If you haven't heard about the guidance from the moderators about using Drupal version tags in questions, read what's written in the question "Version Tags in 2017 and onward".
What can the DA Community do, to try to have the DA moderators change their DVT guidance? And so that we will Save the DVT !
The moderators brought this question to my attention. While I don't think the action proposed in the question is productive, I do think it's worth talking about openly.
If I'm reading you correctly, you are concerned that the moderators are overriding the will of the people by ignoring the score on meta answers. As it happens, I had a similar concern several years ago when I was a moderator pro tempore. One particular response seems apt here:
Sometimes folks propose strategies that would break the entire site if followed... And they end up ranked highly because a lot of folks don't particularly like the site they're on, and wish it was the sort of site that gave away more free ice cream and less disemboweling criticism.
One of the reasons version tags are suspect is that they have the ability to break a site. To take the specific example of Drupal, it sounds as if Drupal 8 differs from Drupal 7 in myriad ways. There are currently 24,356 Drupal 7 questions. If, let's say, half of the answers to those questions are still valid with Drupal 8, that would mean the tag very misleading. People arriving at the site via a Google search, might be mislead into thinking that the answer to their question isn't on the site at all.
On the other hand, if most of the 7 questions are properly tagged, there's an impending problem with 8. What happens when Drupal 9 comes out? Will there need to be a retagging of old questions? It probably makes more sense to assume all questions apply to the latest version unless proven otherwise. In other words, 8 is premature.
I won't pretend to have all the answers; I have never used any version of Drupal, afterall. But I do know (from several years as a community manager and several years before that as a moderator) that this sort of community policy requires a bit of nuance and a lot of time. As far as I can tell, the policy proposed by the moderators is careful, conservative and constructive. They aren't suggesting Drupal Version Tags be eliminated. Instead, they are proposing a compromise: use the tags when necessary and edit them out when not. What's needed now is a bit of time to try it out and find what, if any, problems occur.
Discouragement sounds like a drastic word, I think. "The use of version tags is discouraged." Ay ay ay. But in the end - if I understand it right now - all this is about is that we are asked to use version tags more carefully.
There's no need to save anything. Because, actually, we still will have version tags. It's just, that they are not always needed.
There are already some examples in the other posts which show that there are really a lot of questions that don't need a version tag at all. Version tags should instead highlight noticeable differences in certain aspects of different Drupal versions.
If we would go on with version-tagging every single post on Drupal.SE we will end up with a lot of nearly duplicate questions. All that would make them different is a version tag and some few characters marking a minor code difference. Does that sound like a powerful collection of really relevant answers? I don't think so.
One of the biggest powers of this community is to foster this infinitely growing collection of questions and answers. One of the most useful actions in the internet in general - I think - is curating content. So I vote to follow the initiative to use version tags only when they are really necessary to highlight a major difference between Drupal versions.
