Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Recently I have noticed quite a few issues switch version, like this:
Version: 7.69 » 10.0.x-dev
It seems like the issue Version selector has been slimmed down, so it's not possible to select for example 7.71 but only 7.x-dev. Is this on purpose?
Comments
Comment #2
drumm#2691889: Add option to remove tagged releases from the version selector is the issue where this change was made. It is an option for each project’s maintainers to decide.
There was some gap between when this configuration change was made by core maintainers and #2847734: Bulk update core issues from tagged releases to dev versions. Issues updated before that update would have defaulted to the first version option, 10.0.x-dev, and be saved that way if they didn’t catch the change.
Comment #3
ressaThanks, but I think it is mostly a challenge with Drupal issues, not so much modules, they seem fine, and still include detailed version. Or would this start happening, if module maintainers decide to use this limited format?
I think it is pretty useful to be able to see if an issue is filed against 7.10 or 7.69, like in the issue I linked to as an example, 7.x-dev could be any of those. I take it has been actively decided to use 7.x-dev, rather than for example 7.10 in the Drupal issue queue under drupal.org/project/drupal/issues, I linked to as an example?
Also, like @dww comments, which I agree with, using 7.x-dev seems counter-intuitive:
The Version list in the search form at https://www.drupal.org/project/issues/drupal seems to have duplicates ... or I am not sure if I understand the difference between
All 10.0.*and10.0.x-dev. Aren't they the same?Comment #4
drummEvery project maintainer has the option to not offer the tagged release versions as options. It is up to maintainers of each project to decide.
Right now, they are effectively the same. When
10.1.x-devis created, it won’t be included inAll 10.0.*.Comment #5
ressaThanks for clarifying. I am still not entirely sure I get the distinction ... so perhaps
10.0.x-devin the search form is the actual dev-release, and only ever a single entity, whereasAll 10.0.*includes10.0.1,10.0.2, etc.? I think also having10.0.x-devmeaning every version 10 release in the issue form Version field (here) throws me off. I might just need to use it, to understand it.Comment #6
drummYep, that's true.
10.0.x-devis an exact match for the dev branch release.All 10.0.*includes all 10.0.* releases, if they are offered as options.