Background information

Release notes

Instructions

  1. Read over the 10.3.0 release notes draft. The section at the top is the initial outline for the release notes. The sections at the bottom need to be completed.
  2. Make sure that all Issues tagged '10.3.0 release notes are included in the release notes.
  3. Review the format of the release notes, and leave comments on the Google doc where something seems incorrect:
    • Ensure that every release note describes a disruptive change. Additions without any disruptive changes belong in the release highlights post, not the release notes.
    • Ensure that every release note follows the release note snippet best practices.
    • Ensure that every release note (save those about a dependency update) includes a link to a change record.
    • Ensure that release notes are formatted correctly in bulleted lists, and that each list item has a blank newline between the tag and the list item text. For example:
      <li>

A disruptive change is described here. For more information, review <a href="">the change record about what-and-such</a>.

</li>
    • Follow the rough organization suggested by committers. If you think something belongs in a different section, leave a comment.
  4. Use the Google Docs "suggestion" feature to suggest corrections, readability improvements, etc.
  5. Comment on this issue to receive credit for working on the release notes.

Issues tagged '10.3.0 release notes'

Comments

xjm created an issue. See original summary.

xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes
xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes
xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes

xjm credited quietone.

xjm’s picture

xjm
she/her
Primary language English
commented
xjm’s picture

xjm
she/her
Primary language English
commented

Oops, wrong issue.

xjm credited catch.

xjm’s picture

xjm
she/her
Primary language English
commented

xjm credited longwave.

xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes
Status: Active » Needs review

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.

xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes
smustgrave’s picture

smustgrave commented

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

smustgrave’s picture

smustgrave commented
Status: Needs review » Postponed

I'm assuming this is actually postponed

#3441010: Container compile crash when a service decorates a destructable service is in the list but is currently NW
#3298701: ImageStyleDownloadController routes do not limit schemes served is merged but release note needs a new review.

xjm credited DamienMcKenna.

xjm credited fgm.

xjm’s picture

xjm
she/her
Primary language English
commented
xjm’s picture

xjm
she/her
Primary language English
commented
Status: Postponed » Active

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

xjm’s picture

xjm
she/her
Primary language English
commented
Status: Active » Needs review

Better status.

smustgrave’s picture

smustgrave commented

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

neclimdul’s picture

neclimdul
He/Him
commented

Don't see it in the gdoc but #144538: User logout is vulnerable to CSRF 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.

xjm’s picture

xjm
she/her
Primary language English
commented

@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 #144538: User logout is vulnerable to CSRF for a release note snippet.

smustgrave’s picture

smustgrave commented

@xjm sorry I was referring to #3441010: Container compile crash when a service decorates a destructable service

xjm’s picture

xjm
she/her
Primary language English
commented

@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.

xjm’s picture

xjm
she/her
Primary language English
commented

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

pameeela’s picture

pameeela commented

Edit: Oops commented on the wrong issue!

nicxvan’s picture

nicxvan commented

I tagged two more issues:

#3333401: Pager h4 causes accessibility flag on many pages
#3439439: Remove country setting from the installer

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.

nicxvan’s picture

nicxvan commented

Also #3333418: Fix pager h4 for accessibility on Stable9 was already tagged, but I don't see it in the release notes.

xjm’s picture

xjm
she/her
Primary language English
commented

@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.

nicxvan’s picture

nicxvan commented

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)
#3333401: Pager h4 causes accessibility flag on many pages
#3333418: Fix pager h4 for accessibility on Stable9
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:
#3439439: Remove country setting from the installer

smustgrave’s picture

smustgrave commented

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?

pameeela’s picture

pameeela commented

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

nicxvan’s picture

nicxvan commented

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 so these probably can stay in highlights unless someone disagrees.

I think my confusion stemmed from this comment asking for a release note: https://www.drupal.org/project/drupal/issues/3333418#comment-14886507
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.

smustgrave’s picture

smustgrave commented
Status: Needs review » Reviewed & tested by the community

With 10.3.0 out should this be marked fixed?

catch’s picture

catch
he/him
Primary language English
commented
Status: Reviewed & tested by the community » 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).

xjm’s picture

xjm
she/her
Primary language English
commented

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

Status: Fixed » Closed (fixed)

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

idebr’s picture

idebr commented

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:
#2519362: Redesign the menu link add form to be less overwhelming
#3432183: Move system/base component CSS to respective libraries where they exist
#2936995: Add taxonomy term revision UI

Can these highlights be merged into the release notes?

xjm’s picture

xjm
she/her
Primary language English
commented

Amending attribution.

quietone’s picture

quietone commented
Version: 11.x-dev » 10.3.x-dev