Problem/Motivation

Contrib projects version string is very confusing with lots of "8.x-*" releases.

Steps to reproduce

Proposed resolution

Enforce to use semantic versions for all projects for Drupal 10.
Drupal 10 must not install a module, theme, etc if the project does not use a correct version string.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

Pasqualle created an issue. See original summary.

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented
Status: Active » Postponed

Postponing based on comments from catch:

If you wanted to enforce it, I'd suggest trying to do it for new releases on d.o if anywhere - that way it will filter through new releases but not old ones.
Drupal doesn't actually care about module versions at all - you don't have to have one, or it could be set to anything, and it'll install fine.
But this seems like something that will eventually sort itself out via new releases anyway.

Hopefully the issue can be closed when D10 is released, as 8.x-* modules will "fade out" by then, or the issue could be moved to the d.o customization project to improve the situation.

tr’s picture

tr commented

It is semantically wrong to rename (for example) 8.x-1.9 to 2.0.0 unless you have made API changes or other changes consistent with a new major version.

What is the point of supporting semantic versioning if we don't use it correctly?

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented

The point is to start using semantic versioning, as 8.x-1.9 is obviosly not a semantic version.

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented
Related issues: +#3009338: [META] Support semantic versioning for extensions (modules, themes, etc) in Drupal core, and allow modules to be compatible with Drupal 8 and 9 at the same time

Version: 10.0.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.