Open
Description
Release scheduled for February 18, 2pm - 5pm PT
Pre-release tasks
- Merge commits (@quicksketch)
- Create the next bugfix milestone (@quicksketch)
- Move all unfinished issues to the next bugfix release milestone (@quicksketch)
- Review all closed issues in milestone: (@quicksketch)
- Issue titles should include a complete, but very brief summary of the problem.
- Bug issue titles should start with
Fix
orFixed
, - New feature issue titles should start with
Add
orAdded
. - Each issue should have accurate labels, especially the "type - " labels.
- Close the milestone (@quicksketch)
- Draft Release notes (@quicksketch)
- Include a short, descriptive summary of the release, for example:
- "Maintenance release for Backdrop CMS. This update contains bug fixes and usability improvements only."
- 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
- Use the text
- Note if any changes were made to files outside the
- Include a section heading
**Changes since version 1.xx.x** are listed below.
- 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/paste contents into release notes draft.
- Remove any square brackets in the titles, and move those issues to their own section.
- Include a short, descriptive summary of the release, for example:
Release tasks
- Update bootstrap.inc with version number (@quicksketch)
- Tag for release, and push tag to GitHub (@quicksketch)
- Revert version number back (@quicksketch)
- Create release notes on GitHub, and publish release (@quicksketch)
- Update the front page download link on b.org (@quicksketch)
- Post/Tweet/Toot/Skeet that a new release is out (assignments below)
- Use text like "There is a bug-fix release out for #BackdropCMS today, version 1.27.2: https://backdropcms.org."
- Post to Bluesky @stpaultim
- Post to Mastodon @stpaultim
- Post to Twitter @stpaultim
Immediate Post-release tasks
- Update Tugboat @quicksketch
- Update Composer @herbdool
- Update Docker @Wylbur
- Update Pantheon @herbdool
- Update Platform.sh @herbdool
- Update Amezmo @jenlampton
- Update DrupalForge @izmeez
- Update the Wikipedia articles @klonos
Backdrop's Website updates
- backdropcms.org @jenlampton (or bugfolder)
- beta.backdropcms.org @bugfolder (or jenlampton)
- docs.backdropcms.org @jenlampton (or bugfolder)
- events.backdropcms.org @jenlampton (or bugfolder)
- forum.backdropcms.org @jenlampton (or bugfolder)
- localize.backdropcms.org @jenlampton (or bugfolder)
See Also
This is a stand-alone release.
Activity