Is m4032404 still being maintained?

I contacted @suzymasri, via the contact form on drupal.org. @skwashd didn't have the contact form enabled, so I was unable to contact him.

I've just taken up the mantle, but I'm still on hold until 20th June (1am GMT+10 + admin time) pending @suzymasri responding here:
💬 Offer to co-maintain 403 to 404 Active
They've logged in this past October 15th 2024, so it means waiting out another 14 days after the initial 14 days waiting for their reply. As best I can tell, Suzy doesn't work at the same company any longer so they're probably not getting the emails, but that's just the rules.

Dave (@skwashd) did respond via email, but he's deferred management of the module maintainers over to Suzy, who was directly looped into the email. Alas, no response that way either.

Anyway, I've got the 8.x-1.x branch fully patched up ready to push and release (along with updated code for each of the RTBC issues to push so it's all hunky dory), and a new 2.0.x branch with Drupal 11 support ready for release too.

Those will be released on the 20th, and I'll be opting the project into security coverage.

@elc Apologies again for the late response, you should now have co-maintainer access. I just replied to the co-maintainer request.

Hi @suzymasri ! Glad to see you're still around. I had lost hope and was just waiting for the clock to tick down.

I've only been granted some of the permissions needed to be a co-maint as I can't currently make releases, re-open issues, or edit the project page to "Opt into security advisory coverage".

The default branch will need to be switched over to the new one when I get that far too, but that can be handled by yourself or @skwashd when it comes up. It requires maintain maintainers permission for me to grant the ability to do it.

We're all prepped to release: 🌱 8.x-1.0 and 2.0.0 releases Active

I just re-read my permissions and it turns out I have been granted the ability administer releases already - sorry about that as it's hard to tell from my account what I have been granted to do on a project as I don't want to step on toes by over-reaching.

Without "Edit project" I'm not meant to be opting the project into security coverage, but that's was the goal of 💬 Stable 8.x, 9.x, 10.x, 11.x release with security coverage Active .

Anyway, let's go make those releases.

@elc Great! I've also given you edit project and maintain issues permissions. Let me know how it goes and if anything else is needed :)

All good here @suzymasri. Just fixing up my muck up 📌 Method to bypass redirection (Temporary) Active so there will be another release very soon.

If you could as a maintainer:
- update the default branch to 2.x in https://git.drupalcode.org/project/m4032404/-/settings/repository#branch...
- turn off "Enable merge trains" in https://git.drupalcode.org/project/m4032404/-/settings/merge_requests

2.x is where MR should default to, and there's no need to default to using merge trains in a project where only a single MR is probably going to be merged at the one time. Nothing more annoying than accidentally starting a merge train as it's 3x pipeline runs instead of a 5 second immediate merge.