[policy, no patch] Adopt a regular two year release cadence for major releases

We usually use remaining task for things to do on this issue, but the linked discussion was not go be done here, so made that clearer.

All this looks accurate to me! We'll need followup tasks to update the handbook documentation and possibly make a short core blog post, but policy-wise this reflects the reasoning and the committer consensus.

Edited the issue summary to try to have something more documentation-friendly.

This has been waiting on documentation updates and an announcement to close out, but I think 🌱 [policy] Decide how long major Drupal versions should be supported Needs review is getting close, so it might make sense to combine the two. The release cycle page already mentioned that major releases will happen every two years. I added Drupal 10/11/12 examples per the issue summary in https://www.drupal.org/node/3357384/revisions/view/13141233/13224028 →

Given that I think we can mark this fixed, and prepare an announcement when 🌱 [policy] Decide how long major Drupal versions should be supported Needs review is RTBC.

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

I have been meaning to come back here and clarify that the possible release windows for a major release are June, August and December not June, September and December. This caught me out to and was clarified in discussion with the other release managers. This was just human error in typing the issue summary. The release schedule overview page → has just been updated and correctly states June, August and December. I am also updating the Issue Summary here.