Remove next major core version field from project pages

See also https://drupal.slack.com/archives/C03L6441E1W/p1717485876825039

My conclusion from that thread: rather remove that pledge field rather than enhancing or generalizing it. Making it more general would require maintainers to update their content in that field, which most likely wouldn't happen in too many cases. And enhancing it may not provide enough value as the supported versions are now clearly visible on project pages (release list), in project browser, and elsewhere.

I think generalizing it is confusing, because once Drupal 11 is out, "next major version of Drupal" will be Drupal 12 immediately :P So possibly removing it is a better idea.

I think removing the dedicated field fine and encouraging maintainers to add whatever is relevant within the project page body. In the past many did this with version 7 vs 8 etc

Besides the aforementioned textfield, there is another example of legacy Drupal core versions that seem to be „hardcoded” on a D․org page:



Probably we want to fix both of them in one run.

@Balu Ertl: I think that's an entirely separate question :) Retitled this from the original suggestion to the consensus. :)

I went ahead and deleted the @drupal8changes block from https://www.drupal.org/list-changes/drupal → , since it is just a block, and wasn’t in code anywhere.

Next steps for the field on project pages:

• Remove the display, other references to it, and field configuration
• Make a backup
• Remove the field

This field is now gone, backup of its data is attached.

Automatically closed - issue fixed for 2 weeks with no activity.