Defer disruptive 10.3 deprecations for removal until 12.0

Probably an good idea to be carefull in the coming months. The cycle this time is short and making the transition easy will help a lot in maintaining a positive view on the release cycle of Drupal.

A definitive set of rules on this will indeed be hard, i don't think we'd be able to make a full edgecaseless rule about this.

Adding a note about module/theme deprecations.

Hm, are you saying we defered the issues themselves to sit for a year or we added the deprecation with a target of 10.1? I remember scripting around deprecations for future versions in both deprecation_status and upgrade status, so I don't think that would be new? Eg. my chart data collection is based on these CLI commands, where I already filter out Drupal 12 targeted deprecations, but I think there is only one of these in core so far:

    // $ grep -r "@deprecated" core --exclude-dir=node_modules | wc -l
    // $ grep -r "@deprecated" core --exclude-dir=node_modules | grep -o "12.0.0" | wc -l

Hm, are you saying we defered the issues themselves to sit for a year or we added the deprecation with a target of 10.1?

I think we did a bit of both in the end. Or maybe I was thinking of 8-9 and we'd already fixed this for 9-10, #3225792: Allow core deprecation testing to distinguish between major versions → is the issue I was thinking about.

Hm … I wonder if #3225792-11: Allow core deprecation testing to distinguish between major versions → could be the mechanism to use here?

Fixing related issue link.

We've been doing this in practice since 10.3.x was branched and so far nothing tricky has come up, so being bold and marking RTBC.

Added a child issue I'm rector since I don't think this is currently possible. Next major seems assumed.

I made the following edit to the 'allowed changes' page - https://www.drupal.org/node/2581501/revisions/view/13351515/13489588 →

Going to go ahead and mark this one fixed.

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