We have a versionless tag for and individual tags for each minor version, eg , and .

Now there's a new tag, .

Should be merged with one of the other qgis tags? If so, which one?

Pros: This would be consistent with how we've handled version tags in the past. QGIS already has a lot of tags. currently has only two questions, so it would be easy to get rid of this tag.

Or should we keep as a standalone tag, to refer to the entire 3.x series?

Pros: The 3.x series is a major change from the 2.x series. The logo changed color from yellow to green, many new features were added, and many old features work differently.

I believe that QGIS 3.0 and QGIS 3.2 are essentially the same series. QGIS 3.4 comes out 26/10/2018 and also belongs in the same series.

Additionally, a lot of plugins and features are being ported to the new versions. I believe our energy would be best used to try and optimise the latest release.

I believe only 2 tags are needed going forwards: and . The tag should refer to the entire "3.x" series. The tags , and should all be merged into .

I believe the tag is not specific enough and will pose the same problem when QGIS 4 comes out in a couple of years.

In support of MapInfoNewbie's answer I would favor to completely remove either all supplement tags ( & ) or the version-less tag , but then I'd like the idea of maintaining major version tags & better, with the reason being that those versions do have significant differences in most aspects of the software.

I also do have the faith that most users will assume the right tag this way, contrary to the current situation and with the continuation of the version-less tag.

The very rare cases where a question refers to QGIS in general, e.g. as a project (and thus possibly being fit for a version-less tag) could be intercepted with e.g. a tag? Does it or do similar tags exist already, and might there be the need to clean up as well?

I have no knowledge of the tag systems capabilities and wouldn't know if this is the way to do this, but: would it be possible to turn all tags prior to the release date of QGIS 3 into the major version tag? Would that, in consequence, mean to manually alter all chronologically following tags according to the major version?

New contributor
ThingumaBob is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
  • 2
    Welcome to Meta. This is answer is tricky, because it has antagonist proposals, so we can't know which one votes (up and down) are supporting/rejecting. I like the idea of removing all version tags, but dislike removing [qgis]. How to vote? In other words, how to decide what to do when it comes the time, if this gets lots of votes? – Andre Silva Sep 18 at 21:04
  • About "would it be possible to turn all qgis tags prior to the release date of QGIS 3 into the major version qgis-2 tag?". Only, with manual edits I believe. Synonymizing and merging actions can only be applied to all questions having a certain tag (no filters allowed). Not 100% sure though. meta.stackexchange.com/questions/70710/…. The last question I did not understand. – Andre Silva Sep 18 at 21:10
  • 1
    @AndreSilva thx, and HI AT ALL here at Meta! yeah a little tricky indeed, as I would agree with reducing either way, but I focus my choice here on the major version tags. let me emphasize more, some bold styled words should do the trick. – ThingumaBob Sep 18 at 21:23

It is not clear in MapInfoNewbie's answer what to do with the tag, hence, I assume the suggestion there (in response to what was asked in question) is just to eliminate/synonymize minor version tags such as and in favour of respectively major version tags and .

I believe we should keep and use version tags only when subject of question is specific to one version or the other. On the other hand, the software version being used can always be specified in the post's body.

The same as suggested in @underdark's answer in Dealing with Q&As using deprecated/non-existent PyQGIS API functions?

In my opinion, answers should specify the version they are written for. If the API changes over time, an update to the answer or a new answer should be added to point out the API change.

I'm not a friend of having ten copies of the same question for ten QGIS versions because it makes it impossible to find and maintain answers.

  • I do like the general idea, too; keeping the main qgis tag and use the versionized tags with care...but in practice, many users won't exactly cooperate with this. And while it is recommended and should be standard, there are tons and tons of questions out there with the first comment asking for version details. – ThingumaBob Sep 18 at 20:19

You must log in to answer this question.

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