10.3.0 release notes

xjm → credited quietone → .

Oops, wrong issue.

xjm → credited catch → .

xjm → credited longwave → .

I updated the draft based on the Drupal 11 beta, the release cycle changes, and the 10.3.0-beta1 and rc1 milestone notes. Also finally fleshed out the IS instructions.

There’s currently 1 issues in RTBC. It’s merged but release note needed some work and gave it a shot

I'm assuming this is actually postponed

🐛 Container compile crash when a service decorates a destructable service Needs work is in the list but is currently NW
🐛 ImageStyleDownloadController routes do not limit schemes served Fixed is merged but release note needs a new review.

xjm → credited DamienMcKenna → .

xjm → credited fgm → .

No, it is actively being worked on because the release comes out in less than a week. Thanks!

Better status.

Should the issue that’s still in work be removed from 10.3 release notes

Don't see it in the gdoc but 🐛 User logout is vulnerable to CSRF Fixed might be a disruptive change for sites. Had some hard coded /user/logout links in some templates which lead to a pretty ugly unthemed confirmation form.

@smustgrave Which issue and which section? Stuff that is still underway is listed under "known issues" on purpose, but is there an issue outside those sections?

@neclimdul, thanks, I reopened 🐛 User logout is vulnerable to CSRF Fixed for a release note snippet.

@xjm sorry I was referring to 🐛 Container compile crash when a service decorates a destructable service Needs work

@smustgrave, Yep, that one is listed under the known issues on purpose, because it's a major bug that could cause problems for people updating to 10.3.

Adding credit for @neclimdul; that's a good find.

Link to the comment 📌 10.3.0 release notes Active

Not much information to go on.

I tagged two more issues:

🐛 Pager h4 causes accessibility flag on many pages Fixed
📌 Remove country setting from the installer Fixed

Re reading this issue summary they probably belong in the highlights rather than release notes.

Let me know where they go and I'll retag them.

Also 🐛 Stable9 accessibility update: Pager h4 causes accessibility flag on many pages RTBC was already tagged, but I don't see it in the release notes.

@nicxvan, correct, only changes that are disruptive should go in the release notes. The release notes should describe the disruption the site owners or module developers need to address and how.

If it's just an improvement or feature, it should be tagged for the highlights instead.

I don't have time at the moment to look over these three issues, but if they are disruptive, then the release notes should be updated to describe what the disruption is, who is affected, and what they need to do to fix it, with a link to the change record. For more information and examples, see the release note snippet documentation → .

Leaving NR to check back on them.

In that case the pager ones are likely highlights since they are accessibility improvements (They were split up since one of them was for stable9)
🐛 Pager h4 causes accessibility flag on many pages Fixed
🐛 Stable9 accessibility update: Pager h4 causes accessibility flag on many pages RTBC
I've retagged those two already.

The country default in the installer is likely disruptive if someone is expecting that default to be set. It was not used in core and low usage in contrib, but likely qualifies for release notes:
📌 Remove country setting from the installer Fixed

Will say about the pager ones though. Even though they aren't disruptive any module that ships with a view config file will need to be updated for future installs right?

Edit: going to move my comment to the specific issue.

After reading the comment from @pameeela I don't think the country setting needs a release note.

@smustgrave that is a good point, I think since we added config new config we didn't hit the circular issue @dww hit here: https://www.drupal.org/project/drupal/issues/2640994#comment-15597379 🐛 Label token replacement for views entity reference arguments not working Needs work so these probably can stay in highlights unless someone disagrees.

I think my confusion stemmed from this comment: https://www.drupal.org/project/drupal/issues/3333418#comment-14886507 🐛 Stable9 accessibility update: Pager h4 causes accessibility flag on many pages RTBC
and since that issue was a follow up I assumed the parent needed release notes too, but based on the docs I think they fit better under highlights.

With 10.3.0 out should this be marked fixed?

Yep we can close this now (still possible to add issues to the release notes now the release it's out if something comes up).

I was leaving it open on purpose to remind myself to look at #28 and #29 once more info was provided.

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

It seems that many of the issues tagged with "10.3.0 release highlights" didn't make it to the release notes: https://www.drupal.org/project/issues/search?issue_tags=10.3.0%20release... →

Several issues I have ran into in customer projects weren't mentioned, for example:
📌 Redesign the menu link add form to be less overwhelming Fixed
📌 Move system/base component CSS to respective libraries where they exist Fixed
📌 Add taxonomy term revision UI RTBC

Can these highlights be merged into the release notes?