Skip to content

Backdrop 1.33.0-preview Release checklist #7044

@jenlampton

Description

@jenlampton

Scheduled for January 5th, 2026

Pre-release tasks

  • If this is the Jan 1 pre-release, then make sure to update the end year in the "All Backdrop code is Copyright..." section towards the bottom of the README.md file (Issue #7044: Updating README for 2026. backdrop#5189). @quicksketch
  • Merge commits @quicksketch
  • Create a new minor release milestone
  • Move all unfinished issues to the next minor release milestone @quicksketch
  • Review all closed issues in milestone: @jenlampton
  • Draft Release notes @quicksketch
    • Include a short, descriptive summary of the release, for example:
      • This is the preview release of Backdrop 1.16.0. Please use this version if you would like to help us test the features in the new version of Backdrop prior to the official release on January/May/September 15th, 20xx.
    • Include a section heading ## Notes for updating*
      • Note if any changes were made to files outside the core directory, for example:
        • - No changes have been made to the `.htaccess`, `robots.txt` or default `settings.php` files in this release. Updating customized versions of those files is not necessary.
        • See this example for updates to .htaccess
        • See this example or this example for updates to settings.php
      • Note if updates (update.php) needs to be run, for example:
        • Use the text The database update script does **not** need to be run.
        • or **It will be necessary to run the update script** (located at /core/update.php) for this release.
        • Note: you can use this command to see if any install files were changed:
          ls -1 core/modules/*/*.install | while read filename; do echo "$(git log -1 --pretty="format:%ad %f" --date=format:"%F %R" -- $filename)" $filename; done|sort
    • Include a section heading ## Changes since version 1.xx.x
      • navigate to Actions
      • Select the most recent time "Release Notes Generator" has been run.
      • Download the release-notes artifact attached to the generator.
      • Unzip the file, and copy/pate contents into release notes draft.
        • Move the headings to H3, add another # before the ## to get ###.
      • Re-word issue titles to indicate that the problems have been fixed.

Pre-release Publicity + documentation tasks

Release tasks

  • Update bootstrap.inc with version number @quicksketch
  • Tag for release, and push tag to GitHub @quicksketch
    • Note: New incremented branch for development is usually created on release day
  • Revert version number back on 1.x branch with the same minor number (e.g. 1.10.x-dev) @quicksketch
  • Create release notes on GitHub Important: Check "This is a pre-release" checkbox when creating release @jenlampton

Website updates (optional)

Post-release Publicity + documentation tasks

  • Post/Tweet/Toot/Skeet that a new release is out (assignments below)

See Also

  • Minor Release Checklist (coming soon)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions