Background information

Instructions

  1. [DONE] Read over the beta release draft outline. The section at the top is the initial outline for the beta release notes. The sections at the bottom contain the update information from previous releases.
  2. [DONE] The first task is to consolidate the update information from the alpha releases into the beta notes draft.
    • If a change was backported to 9.4, suggest deleting it and indicate that it was backported in the comment thread.
    • If a chance was not backported to 9.4, move individual notes from the alpha section at the bottom to the appropriate headers in the outline.
      • Use the Google docs "suggest" feature to paste the snippet in the outline, and cut it from the alpha section to indicate it's been addressed.
      • Leave a comment on your suggested deletion in the alpha section documenting where the note has been added in the beta outline above.
    • For now, do not move dependency update information to the outline. These need to be consolidated later based on the full changes between 9.5 and 10.0. (Dependency additions and removals can still be populated now.)
  3. [DONE] The next task is to consolidate the dependency update information from the alphas. Some dependencies might be updated multiple times over the alpha phase, so it is important to consolidate the information for each dependency.
    • Keep the important information from each release note, and change the text to indicate the full change from 9.5.
    • To review the overall changes in Composer production dependency requirements from 9.5, use:
      git diff 9.5.x 10.0.x -- core/composer.json
    • To review overall changes for Composer development dependency requirements, use:
      git diff 9.5.x 10.0.x -- composer.json
    • To review changes to JavaScript production and development dependency requirements, use:
      git diff 9.5.x 10.0.x -- core/package.json
      

      Note that production dependencies will have a constraint beginning with ~, whereas development dependencies will have a constraint beginning with ^. Modernizr will not be listed.

      You can also double-check changes to the production JavaScript dependencies with:

      git diff 9.5.x 10.0.x --stat -- core/assets/vendor/

    • If in any case the release note references an older version than what is actually in HEAD, correct the version and look for the issue that updated it.
    • If the release note mentions a newer version than what is present in the constraints, it may be referring to the version used in the core composer.lock and metapackages. You can review these with:
      git diff 9.5.x 10.0.x -- composer/Metapackage/CoreRecommended/composer.json
      git diff 9.5.x 10.0.x -- composer/Metapackage/DevDependencies/composer.json 
      

      In most cases, the Drupal 10 release notes do not need to mention minor- or patch-level updates to lockfile versions of dependencies individually. Only major-version updates (or minor-version constraint increases different from 9.5) need to be mentioned.

  4. [DONE] Changes since alpha7 (up until 2022-09-15 22:45 CET)

    Going through issues updated since 7th of September, checking if the release note snippet is added to the draft.

    Issue Present Comment
    #3267515: Remove RDF from core
    #3306210: Remove Farbtastic library from core Added
    #3309319: Manually test upgrade core Classy to contrib Classy
    #3309176: Remove Stable theme from Drupal 10
    #3308890: Deprecate Stable theme
    #3278415: Remove usages of the JavaScript ES6 build step, the build step itself, and associated dev dependencies Already present from other issue (#3278246: Deprecate core/scripts/js/babel-es6-build.js for removal from 10.0.x)
    #3301545: Remove popperjs from Drupal 10
    #3270438: Remove CKEditor 4 from core
    #3227033: Remove Quick Edit from core
    #3298396: Upgrade composer requirement to 2.3.6 to prevent warnings on PHP 8.2
    #3293090: Fail JavaScript tests on JavaScript errors Wrote a release note snippet in issue and added it to the draft.
    #3255749: Composer v2.2 prompts to authorize plugins Already present
    #3290810: Remove updates added prior to 9.4.0 (9.4.4 for ckeditor) and add 9.4.0 database dumps Present in alpha 2
    #1040534: Rewrite rules for gzipped CSS and JavaScript aggregates cause lots of lstats for files that will never exist
    #3306153: Update CKEditor 5 to 35.1.0 Added in 9.4 and 9.5, not in 10
    #2531564: Fix leaky and brittle container serialization solution Already present
    #3308826: Update eslint-plugin-yml to 1.2.0 Already present
    #3261163: Update to PostCSS 8 Already present
    #3308821: Update stylelint-config-standard to 28.0.0 Added
    [#]
  5. Comment on this issue to receive credit for working on the release notes.

Comments

xjm created an issue. See original summary.

xjm’s picture

Issue summary: View changes
xjm’s picture

Issue summary: View changes
xjm’s picture

xjm credited phenaproxima.

xjm credited quietone.

xjm’s picture

xjm’s picture

Issue summary: View changes

xjm credited FeyP.

xjm’s picture

xjm’s picture

Issue summary: View changes
xjm’s picture

Issue summary: View changes
xjm’s picture

Issue summary: View changes

xjm credited bbrala.

xjm credited lauriii.

xjm credited nod_.

xjm credited Wim Leers.

xjm’s picture

bbrala’s picture

Issue summary: View changes

Went through the link provided by @xjm to see if all release notes were added.

Hopefully my table formats well ;)

bbrala’s picture

Issue summary: View changes
bbrala’s picture

Issue summary: View changes
bbrala’s picture

Issue summary: View changes
bbrala’s picture

Issue summary: View changes

Added 4 new issues that are on the todo list since my check yesterday, did not check release noted for existance and such.

bbrala’s picture

Issue summary: View changes
bbrala’s picture

Issue summary: View changes
bbrala’s picture

The IS mentiones: "up until 2022-09-15 22:45 CET". Will beta be tagged at that specific moment, or would new commits still be tagged?

longwave’s picture

@bbrala as I understand it, that is the commit freeze time so nothing release-note-worthy should be committed after that date, but critical bug fixes may still make it in.

I made a number of suggestions to the release notes yesterday, so also commenting for credit :)

bbrala’s picture

Issue summary: View changes
bbrala’s picture

Issue summary: View changes
bbrala’s picture

@phenaproxima has been adding the release note snippets left and right. Thank you :)

bbrala’s picture

Issue summary: View changes
xjm’s picture

xjm’s picture

Issue summary: View changes
Status: Active » Fixed

Thanks to everyone who helped put this together! 💪

Status: Fixed » Closed (fixed)

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