Merge 5.x branch into the 3.x branch and create stable release dropping Drupal 8 support

https://www.drupal.org/project/usage/features → shows a few hundred installs of either the dev or alpha1 release on the 5.x branch. If further D9 and D10 compatible releases are made on the 3.x branch, those installs presumably won't get update notices but would of course receive notification of a decision to no longer maintain the 5.x branch. It could help to document in advance a plan for how this will work.

Yeah I think the plan would be to mark that branch as unsupported first and in say one month remove the branch and the alpha release.

This also drops support for Drush 9 and adds support for Drush 11.

Dave Reid → closed merge request !27

Looks like this is passing everywhere, ready for review!

Just to be clear: "that" branch you want to remove soon is 3.x, is it not ?

No, I believe (with no malicious intent) that a 5.x branch was premature, that there are no major changes or backwards-compatible changes other than dropping support for Drupal 8, and it would be better to allow people to upgrade to a Drupal 10-compatible version on their sites rather than have to manually change their composer dependency. We have way more users of 3.x than 5.x since it was only released mid-April and only in an alpha1 state with a note about "Updating to releases on this branch is not yet recommended, pending confirmation of a plan for ongoing maintenance." The plan for ongoing maintenance is to drop that branch and continue the work in 3.x that will help the majority of the modules' users.

OK. As long as we have a last tag for the last 3.x D8 compatible version before removing compatibility, it should be fine indeed.

@fgm: Are you saying you need a Drupal 8 compatible new tag first?

shows a few hundred installs of either the dev or alpha1 release on the 5.x branch.

Yeah I think the plan would be to mark that branch as unsupported first and in say one month remove the branch and the alpha release.

As one of the organizations using the 5.x branch currently, we have made note of the trajectory of going back to 3.x releases and will switch when a Drupal 10 release of 3.x is available. But we would appreciate a grace period of leaving the 5.x branch unsupported and the branch not yet removed.

Removing the alpha release/tag at all seems like it could have impacts, though, for sites that are using automated build processes for their sites. At best, it will cause automated builds to fail and not deploy, but if, say, someone is doing composer installs in a production environment (we're not, to big clear), it could cause a site outage.

Therefore, I request that the 5.0.0-alpha tag either never be deleted, or there be a longer grace period. Thanks!

Yeah I think we just turn off the "supported" flag for now but leave the tag and release out there to be "hidden" for a while. I don't see any urgency around deleting the branch/release right now vs getting a new 3.x tag out.

Speaking as one of the organizations that used the 5.x branch to have Drupal 10 compatibility. I would have preferred to have an update 3.x branch released at the same time or close to when the 5.x branch was marked as unsupported. Do we have a timeframe on when a Drupal 10 version will be released so those of us that are on Drupal 10 can use a supported version of the module?

We are getting a release out today, sorry about the blip in coverage for those using 5.x.

Reviewed the code in GitLab. This merge request was already running on Drupal 10 websites. The D10 test is passing and D9 with 3 versions of PHP. Let's merge this in and cut a new stable release.

This fix is merged into 3.x-dev. We are going to commit a few more issues and then cut a new stable release for the 3.x branch.

Features version 8.x-3.13 is released → that drops support for D8 and adds support for D10. Great work community! Thank you for your contributions.

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