- Issue created by @trackleft2
The naming of the current default legacy development branch 8.x-1.x does not follow the standards of semantic versioning which seem to be preferred now, see:
Besides, module's new development branch 2.0.x appears to properly apply these standards which seem to work quite well for the creation of tagged stable releases.
Examples of the similar issue for other modules:
Important note:
Based on the documentation:
Transitioning from 8.x-* to semantic versioning →
When your project switches to using semantic versioning, you must increment your major version. For example, if the latest release is
8.x-3.5, your next stable release will be4.0.0
Which means that in our case transitioning from 8.x-1.0 would bring us to 2.0.0, which is available 2.0.x).
Active
1.0
Miscellaneous