Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Problem/Motivation
We added the drupal.org issues link to projects so projects without Drupal 9 plans would get useful stepping points for dealing with collaboration with projects. That said, there is 2 problems with this:
1. The drupal.org issue links are replaced with Drupal 9 plans when scanning is done. Then the issue link is not available anymore.
2. The Drupal 9 plan is only pulled when scanning, even though for projects where you want to collaborate with the maintainer, you may not want to start off scanning locally anymore for example. So you don't get the Drupal 9 plan in this case.
Steps to reproduce
Proposed resolution
Discuss.
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 3168912.patch | 125.71 KB | Gábor Hojtsy |
Comments
Comment #3
Gábor HojtsyCrediting @Kristen Pol for her raising this in #3165529: Various feedback on 8.x-3.x.
Comment #4
Gábor HojtsyI've been thinking a lot about how to pre-seed the list with a bunch of Drupal 9 plans fast without checking each project one by one. We actually have that kind of data for deprecation_status in a drupal.org dump. We can take a filtered version of that and ship with the module now that the plans don't change too much. Then we can overload that with the actively obtained Drupal 9 plan when we have it. I also realized that we can keep the Drupal 9 issue search link at all times and would use less space if we make it an explicit column.
Comment #6
Gábor HojtsyFixed the link transformation code and committed. Woot!