Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 153 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

There have been several proposals and questions around the merge of version tags into the main tag.

The current state is to allow version tags and I agree with that. However, I would suggest to avoid versioning deeper that the major release.

I propose is to merge , into and apply the same to , , etc in the future.

The reason is the following.

We currently have , , and (and several other 2.x tags).

Given that Rails is going to release a minor release every 6 months, we're likely going to have , , etc in the near future.

The problem is that questions tagged with a version tag are, in the majority of cases, mis-tagged. Users working with a 3.x version tend to tag the question with any 3.x tag available even if, in most cases, the version tag is completely irrelevant.

enter image description here

There are very little differences between and . Of course, a greater release can contain features not available in the previous minor version, but in terms of answer to a question, the solution is never drastically different. This is not true for major versions.

Moreover, the current configuration leads to misinterpretation of the major version tag. For instance, is the tag for 3.x questions or for the 3.0? I tend to consider it for 3.x questions, but then it means we're missing . Vice-versa, if we consider it for 3.0 discussions then we are missing the global 3.x tag.

In fact, if we decide that 3.1 and 3.2 versions are so different to justify a tag, it means that also 3.0 is different than 3.1.

Before opening this thread I researched other framework tags, such as and , but I don't have enough experience with them to make an effective comparison. I know, for example, that the development cycle of is very different than and the tags , , probably makes sense because django minor versions are almost major releases (they have been releasing one minor release per year since 1.0 and they are substantially different).

Thus please consider this thread a proposal specific for Ruby on Rails versions.

share|improve this question

You must log in to answer this question.

Browse other questions tagged .