Problem/Motivation

Hi folks! I've been happily using Forward on a client site for many years. I'm finally getting a chance to upgrade from core 8.9.x to 10.6.x. I've run into a series of bugs and issues with Forward. Some of which have already been fixed in 4.0.x-dev but never released (there's been no release since Dec 2022). Others that are sitting in the issue queue awaiting review and commit. There's no .gitlab-ci.yml file here, so MRs do not run any pipelines.

I know all too well the demands on our time as maintainers. I imagine many/all of y'all have moved on to other things. No shade or offense intended. I really get it.

However, since I've got a need, and a client with some funding, I'm willing to step up and become a co-maintainer. My goals would be:

  1. Get GitLab CI running so we can make sure things can be as stable as possible. #3579177: Enable GitLab CI and fix pipelines
  2. Fix the default pipelines if there are PHPCS or PHPStan warnings / errors. #3579177: Enable GitLab CI and fix pipelines
  3. Triage the issue queue and commit any bug fixes that are actually ready to go.
  4. Move other bug fixes along if they need mild help before they're solid.
  5. Whenever feasible, ensure automated test coverage for any bug fixes. #3579221: Harden ForwardFormTest.php to verify email contents (among others)
  6. Cut a new 4.0.3 release. https://www.drupal.org/project/forward/releases/4.0.3
  7. Port to D11, ideally maintaining as much backwards compatibility as possible. #3516841: Drupal 11 compatibility
  8. Cut a 4.0.4 release, or potentially 4.1.0 if we need to drop support for older core versions.

After that, all bets are off. 😂

Maybe if this client is still around and wants to port to D12 in a few years, work on that, too. 😅

Steps to reproduce

Proposed resolution

Add @dww as a full co-maintainer.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

dww created an issue. See original summary.

john.oltman’s picture

Status: Needs review » Fixed

Sounds great, thanks for taking this on! I see that someone added you as a maintainer already, so marking this fixed.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

dww’s picture

Yay, thanks!

Yeah, I had asked in #maintainers Slack where Moshe replied:

Done. Thanks dww. I removed myself too. I don’t recall working on this module.

Cheers,
-Derek

dww’s picture

Issue summary: View changes

Updating the summary based on what I accomplished in a few hours today with no LLM "help". Proudly built and maintained by a human!

joseph.olstad’s picture

Excellent, thanks @dww
btw, I see there's D11 support in 4.0.x-dev, I see you've planned 4.0.4 but are waiting? You could use an rc tag like 4.0.4-rc1 , packagist/ d.o handle the rest, doesn't force others on D10 to upgrade but does offer a tagged release solution for D11.

dww’s picture

@joseph.olstad: See #3516841-10: Drupal 11 compatibility:

Since I *just* cut the 4.0.3 release, and I don't actually need the D11 support immediately for the site I'm working on this for, I'm going to let this simmer in the -dev release for a few days. If anyone is available to do more manual testing, that'd be great! If there are no signs of trouble, I'll cut 4.0.4 to drop D9 and add D11 in the coming days/weeks (but not months/years).

and/or the text I put on the Forward project page:

Drupal 11

The 4.0.x-dev release is now compatible with Drupal 11. Please test it and report any problems. If it's working well, a new 4.0.4 release should be out in the coming weeks. See #3516841: Drupal 11 compatibility for more.

Not worth the churn for our users, nor my time, to do an RC release. If you're interested in helping get another tagged release with D11 support, you can do what I asked: perform some testing, and report your findings.

https://www.drupal.org/project/forward/releases/4.0.x-dev contains the instructions for how to get composer to install the dev release:

composer require 'drupal/forward:4.0.x-dev@dev'

Thanks,
-Derek

Status: Fixed » Closed (fixed)

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