Transition releases from 8.x-* to semantic versioning

IMHO, this project should drop support for Drupal 8 in the next major version release, and may have to for the Drupal Core 10.1 release anyway due to hard-coded paths in the PHPUnit tests that have changed upstream.

Drupal 8 and Drupal 9 are both unsupported.

Saying that I would recommend the following:

• Cut stable 8.x-2.0 release with 8 and 9 support and only do security releases and major bug fixes
• Cut new branch 3.0.x and 3.0.0 from 📌 Automated Drupal 10 compatibility fixes RTBC as it works on Drupal 10.1 but not on Drupal 9. Make it the only recommended release.

Testing issues with D9 and D10 have been mitigated. Same PHPUnit tests will now run with the two different paths for blocks.

Some poor saps are still upgrading D8 sites and are finding they have to fix horribly broken code where D8 has been left on when it shouldn't have been. In this case, there does not seem to have been sufficient changes to warrant removing that version.

It would only be necessary to drop D8, and move to 3.x, when a breaking change is introduced. Otherwise it's just removing the "^8" for the sake of removing it when the code still entirely works.

@ELC you can have two supported versions, like @VladimirAus was saying. As long as there is an upgrade path, I think you're golden and shouldn't have to support old code for unsupported versions.

Either way is fine with me though.

Dropping support for a core version doesn't require a new major version of this module. It only makes it harder for people to upgrade.

Yes, it'd be nice to use semver, but not just for the sake of it. When we have truly breaking changes, we can move to 3.0.x. But until then, I'm going to try to keep this project as easy to upgrade with as possible, which includes not introducing a new major version for nothing.

Thanks,
-Derek

Project has moved to semantic versioning + 1.

Automatically closed - issue fixed for 2 weeks with no activity.