Skip to content

Backdrop 1.33.0 Release checklist #7054

@jenlampton

Description

@jenlampton

Scheduled for January15, 2026 4pm - 10pm PT

Pre-release tasks

  • If this is the Jan 15 release, ensure that the end year in the "All Backdrop code is Copyright..." section towards the bottom of the README.md file has been updated to reflect the new/current year. @quicksketch
  • Merge commits @quicksketch
  • Move all unfinished issues to the next bug-fix release milestone @quicksketch
  • Review all closed issues in milestone: @jenlampton
    • Issue titles should include a complete, but very brief summary of the problem.
  • Close the milestone @jenlampton
  • Draft Release notes @jenlampton
    • Copy Preview release release notes, update as follows
      • Include a short, descriptive summary of the release, for example:
        • The Backdrop community is proud to release version 1.xx of Backdrop CMS, following our 4-month release cycle.
      • 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.
      • Include a section heading ## Changes since version 1.xx.x
        • 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
        • 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.
        • Note: This list can also be copied from the list on the preview release, but review closed issuses in the milestone
      • Verify the list above matches all changes since the most recent bug-fix release

Release tasks

  • Update bootstrap.inc with version number @quicksketch
  • Tag for release, and push tag to GitHub @quicksketch
  • Branch for new minor number (e.g. 1.10.x) and push to GitHub @quicksketch
  • Revert version number back on 1.x branch with minor number increased @quicksketch
  • Revert version number back on new minor number branch @quicksketch
  • Create release notes on GitHub, and publish release @jenlampton
  • Unpublish preview release on backdropcms.org @jenlampton
  • Create a new language template file for the translation server @olafgrabienski

Immediate Post-release tasks

Publicity tasks

Code tasks

Backdrop Website updates

2-week Post-release tasks

Publicity tasks

  • Publish a Public Notification on BackdropCMS.org about the blog post / release. @stpaultim
  • Send a newsletter to subscribers @stpaultim or @jenlampton or whoever has time

See Also

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