- Issue created by @m.abdulqader
- Assigned to julien
- Status changed to Fixed
about 1 year ago 11:47am 6 June 2023 - 🇳🇴Norway gisle Norway
julien,
the person that offered to maintain was m.abdulqader → , not me. I just corrected the issue's metadata. - Status changed to Active
about 1 year ago 11:54am 6 June 2023 - Status changed to Fixed
about 1 year ago 1:30pm 12 June 2023 - 🇳🇴Norway gisle Norway
Thank you for sorting it out. However motivation for the offer was to "create a stable release for Drupal 10". m.abdulqader does not have permission to create releases, so all he can do is to prepare one, and then ask you create a release.
I gave @m.abdulqader the permissions to administer releases, so he can make the release for Drupal 10.
- 🇳🇴Norway gisle Norway
Thank you, I can see from the project's maintainers.json → that he now can do this.
- Status changed to Fixed
about 1 year ago 11:08am 16 June 2023 - Status changed to Fixed
about 1 year ago 12:15pm 16 June 2023 - 🇳🇴Norway gisle Norway
m.abdulqader, please don't change the status of an issue from "Fixed" to "Closed (fixed)". An issue with the status "Fixed" will be automatically closed as fixed and removed from the list of open issues after 14 days. It should remain open for 14 days after being "Fixed" to cater for regressions and other unintended consequences of the fix.
For reference, see item #12 of the "Don't"-list on this note about Issue Etiquette →
Automatically closed - issue fixed for 2 weeks with no activity.