These will no longer work as Drupal 9.* won’t have API compatibilities attached, #3085041: Drupal core 9.x.x releases should not attach API compatibility term
sites/all/modules/drupalorg/drupalorg/drupalorg.module
18:define('DRUPALORG_DOWNLOAD_API_COMPATIBILITY_TID', 7234); // 8.x
sites/all/modules/drupalorg/drupalorg_project/drupalorg_project.module
16:define('DRUPALORG_CORE_DEVELOPMENT_VERSION_TID', '7234');
26:define('DRUPALORG_CORE_STABLE_VERSION_TID', '103');
These can likely use #3087624: Add a field to releases for release category. and/or #3087220: Migrate project_release_supported_versions to store “branch” instead of API/Major
Comment | File | Size | Author |
---|---|---|---|
#5 | Screenshot from 2019-11-19 12-32-04.png | 153.22 KB | catch |
#5 | Screenshot from 2019-11-19 12-31-56.png | 40.9 KB | catch |
Comments
Comment #2
drummComment #4
drummComment #5
catchThis has broken the issue queue links on the contributors block.
Comment #6
drummThe way the code is working out here, it is looking best to limit this to issues on dev releases for now. “8.x+” doesn’t cleanly map to the current options for issue queue filtering at the moment. Selecting every individual release hits some sort of Suhosin or equivalent query parameter limit. And we won’t have 9.x options until #3089291: Group issue version “series” by branch instead of API compatibility is done.
I opened #3095433: Update “Contributor Links” block counts & links to use “branch” version groups as a reminder to follow up on this.
Comment #8
drummThis should be better now.