Automated Drupal 10 compatibility fixes

Checking in with the module maintainers: with this already committed to the 5.0.x branch, would it be possible to get a new release tagged so that sites can require this via the normal Composer methods? Thanks in advance!

You can add https://www.drupal.org/project/features/releases/5.0.x-dev → release to composer and test @mark_fullmer

Any word on when a release will be made for Drupal 10 compliance? I've run the dev release and it seems to be working perfectly. Unfortunately due to security policies at the office we cannot run dev versions and need a stable release. This is one of the last modules we are waiting on to upgrade to Drupal 10 and would really appreciate a stable release when the maintainers get a chance.

I've run the dev release and it seems to be working perfectly. Unfortunately due to security policies at the office we cannot run dev versions and need a stable release. This is one of the last modules we are waiting on to upgrade to Drupal 10 and would really appreciate a stable release when the maintainers get a chance.

+1 to all of this:

- Our team has also tested the 5.0.x-dev branch with Drupal 10 and not encountered any issues
- For policy reasons, we also cannot require branches of projects in our stable releases
- This is also one of the last modules we are waiting on for the Drupal 10 upgrade

Marking as RTBC to reflect two community members vouching that it is functionally compatible with D10.

Hello, I'm here to add one more +1 in support of a D10-compatible release.

An alpha or beta release would be fine, just something other than a dev build, since we have recently run into a technical limitation using a dev
build based on a specific commit hash. We found that you can't rely on getting the same thing every time you do a Composer build without modifying the site's root `composer.json` file, which isn't an option for us with the architecture of our Pantheon custom upstream.

We are on schedule to upgrade ~100 sites from D9 to D10 in May, and this is one of the last remaining contrib modules in our standard distribution that does not have a D10 compatible release. I appreciate all the fine work folks are doing here, and hope this can get pushed over the finish line soon. Please let us know if there is any further labor that can be contributed to the effort in specific issues.

Adding a +1 here too. My team will be upgrading sites to Drupal 10 on May 23rd, and would love to have a stable, Drupal 10 compatible release for the Features module. Thanks for all the work on this!

Thanks for your notes. While I am currently the most active maintainer in Features for Drupal 9, I am not the project owner. I'm not planning to cut a D10 compatible stable release as I am transitioning out of Drupal and therefore won't be maintaining through the new release cycle. It may be time for some of the steps outlined in the documentation page Finding a new project owner or new maintainers/co-maintainers → .

Thanks for clarifying your current relationship to maintainership, nedjo, and thanks for all your work up till now.

One potential win-win would be for you to go ahead and tag a Drupal 10-compatible release from what is current in the 5.0.x branch, and simultaneously mark the project as not actively supported. That would allow folks to composer-require a D10-compatible release and provide patches, as needed, in the short term, to fix any incompatibilities, while not creating an expectation that you provide maintenance during the Drupal 10 release cycle.

Long term, of course, folks should step up to follow the steps in offering to co-maintain this project ( https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... → ).

But a tagged release would be very beneficial in un-blocking people using this site who are trying to update to Drupal 10.

@mark_fuller, okay, I've gone ahead and created a 5.0.0-alpha1 release → and linked to this conversation in the release notes. For now, releases in the 5.0.0 branch is marked supported but not recommended.

Wonderful, @nedjo! The Drupal community thanks you. I'll talk with our team about what we can do to help maintain the Features module going forward.

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

Do we know what the long-term roadmap is for the 5.x version is? There's currently a note on the https://www.drupal.org/project/features/releases/5.0.0-alpha1 → release:

Updating to releases on this branch is not yet recommended, pending confirmation of a plan for ongoing maintenance.

Has this been addressed in any way? Is there a roadmap? Are there major changes we should be aware of in the 5.x branch either currently or incoming, or should this just be a stable release on the 3.x branch?

I'm not really seeing any major differences between the 8.x-3.x branch and the 5.x branch aside from the Drupal 10 changes, would we be opposed to just merging this into 3.x and tagging a new stable release there?

Just a heads up for everyone, we are talking about plans to merge the current 5.x branch into the 8.x-3.x branch and tag a stable release, and then probably get rid of the 5.x branch for now. I think it was only really used for this code and doesn't contain any major changes aside from keeping up to date with Drupal core major versions, so there's no reason for a separate branch really. Unless someone really needs a Drupal 8-only compatible branch, but Drupal 8 is unsupported right now anyway, so it's a moot point.