There are many contributors who are reviewing and testing bot issues even when the maintainers have committed the changes or separately made a compatible release because the bot issue is still marked Needs review. This is a waste of time and energy better spent on other issues.
Go to an issue that's marked Needs review but the bot patch has already been committed or there is a compatible release. Some examples where I manually moved some back to Active. Note that is some cases, the commit does not show up on the bot issue which makes it even less obvious what's going on. The latter can happen due to using a new version number or using a similar patch from another issue.
📌
Automated Drupal 10 compatibility fixes
Fixed
#3296858: Automated Drupal 10 compatibility fixes →
📌
Automated Drupal 10 compatibility fixes
Closed: outdated
#3304027: Automated Drupal 10 compatibility fixes →
1. Update the issue summary and comment templates to recommend that the issue status be changed to Active after the maintainer has committed a bot (or equivalent) patch and to also add a comment when doing so so it's clear to the community.
2. Consider also adding some information to contributors that recommends they check if there is already a compatible version before reviewing/testing and, if finding one, adding a comment and moving to Active.
Note this was discussed in the #d10readiness Slack channel and it was agreed that this was a good idea.
Active
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Moving to project analysis where the code lives now.
Im going through the backlog of issues.
Is this stilla. thing? We've kinda iterated on the issue template a few times. This is the current state: 📌 Automated Drupal 11 compatibility fixes Closed: outdated