plan for Drupal 11 release?

#3369546-4: Automated Drupal 10 compatibility fixes →

The 2.0.x-dev version will install and run on Drupal 11 as well as it runs on D10 or D9 or D8. But there are are still some fundamental problems that have existed since D7 and really need to be resolved - if I make a fixed-point release that gives the impression that the module works, and wastes people's time discovering the same problems that we've known about for years.

The timeline for a fixed-point release is entirely up to the community. There has been no community participation for years, so I work on this when I can and when I need it personally. This module is a mess that I inherited, and it's much more work to clean it up and fix it without breaking existing sites than it would be to start from scratch and create a new module from the ground up. I don't think it's unreasonable to ask that at least some of the 30,000 people who use this module for their website or their business or their job should help out, if it's important to them.

As to your second question, the 2.0.x release will not lose any features over previous releases. I'm not sure what backwards compatibility means in your case, but it's not going to break anything.

"Fixed" status because the "Support request" has been answered.

The timeline for a fixed-point release is entirely up to the community. There has been no community participation for years, so I work on this when I can and when I need it personally.

Thanks, so much, for your ongoing contributions to this module & the Drupal community! Based on the creation of this issue titled "Plan for Drupal 11 release," the activity by joseph.olstad, and speaking for my team, the community is requesting a fixed-point release.

I advocate for proceeding with the release as soon as possible, given the following:
- Drupal 11 core has been released for six months now
- Typically, sites do not and should not use development branches (8.x-1.x) in production, so a release gives indication to the community that the module'scode can be used in production.
- This module is used by 20,000+ sites running on Drupal 8/9/10

As for community participation, we could certainly pursue the paths described at https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... → for encouraging community support of mimemail.

Hello @tr,
I'll clarify my ask here because I was previously confused between 1x and the light grey 2.0.x-dev release that is shown at the bottom of the project page.

1. Please tag a 2.0.0-alpha1 (or beta1) for release on the 2.0.x branch.
2. Mark the 2.0.0-alpha1 release as recommended instead of the 1.0-alpha6 release.

This will accomplish the following:

1. Provides a recommended tagged release for current versions of Drupal (^10.3 and ^11)
2. Makes our upgrades tied to a tag instead of an unpredictable dev branch.
3. Future bug reports will have a specific release version available for issues to be reported against

Thank you!

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