Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

I find that questions related to database topics are frequently dependent on the RDBMS's engine and version.

So when (from reading the question) I can figure out the version, and I know (or suspect) that it is important I edit the question adding the version tag to the existent main tag, say in addition to .

Is it good practice?

share|improve this question
I usually do this on SO, I guess it's a good practice. – j0k Oct 15 '12 at 11:56
Related post: Would specialized version tags be useful? – Aziz Shaikh Oct 15 '12 at 11:58
I certainly think so; unless you actually do have 5 other legitimately useful tags (usually 2 non-version tags is a stretch, like C++ and "time") and it helps sort out the problem of "duplicates" when previous questions for previous versions are now out of date. – Ben Brocka Oct 15 '12 at 12:07
up vote 4 down vote accepted

Version tags should be added when the question is specific for a version, and not for all the versions.

For example, if I ask a question about the user_save() function defined in Drupal 7, I should probably add because the function has been changed in Drupal 7, and its parameters are different from the same function defined in Drupal 6. If I ask a question about the if control statement in PHP, I should not use a version tag, as the if statement is defined in all the PHP versions, and there aren't changes in any of the PHP versions.

Using the generic tag, and the version tag is fine, as it exposes the questions to more users.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .