-
Notifications
You must be signed in to change notification settings - Fork 40
Closed
Labels
Milestone
Description
Release scheduled for April 19, 2023 11:30am - 1:30pm PT
Pre-release tasks
- Merge commits @quicksketch
- Create the next bugfix milestone @jenlampton
- Move all unfinished issues to the next bugfix release milestone @jenlampton
- Review all closed issues in milestone: @jenlampton
- Issue titles should include a complete, but very brief summary of the problem.
- Issue titles sould be in complete sentences, ending with a period.
- Bug issue titles should start with
FixorFixed, - New fearure issue titles should start with
AddorAdded. - Each issue should have accurate labels, especially the "type - " labels.
- Close the milestone @jenlampton
- Draft Release notes @jenlampton
- Include a short, descriptive summary of the release, for example:
- "Security release for Backdrop CMS. This release fixes 1 security vulnerability:"
- Include a list of SA's for commits to this release
- Include a section heading
**Notes for updating**- Note if any changes were made to files outside the
coredirectory, 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 /update.php) for this release.
- 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-notesartifact attached to the generator. - Unzip the file, and copy/pate contents into release notes draft.
- Remove any square bracets in the titles, and move those issues to their own section.
- Include a short, descriptive summary of the release, for example:
- Draft Security Advisories @jenlampton
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 @jenlampton
- Publish Security Advisories on b.org @jenlampton
- Mark the release node on b.org as a security release @jenlampton
- N/A Request a CVE - (assign to jenlampton / quicksketch)
- Update the front page download link on b.org @jenlampton
- Tweet that a new release is out @jenlampton
- Use text like "There is a security release out for #BackdropCMS today, please update when you can. Backdrop core - Critical - Third-party libraries - BACKDROP-SA-CORE-2021-001"
Immediate Post-release tasks
- Update Tugboat @BWpanda
- Update Pantheon @herbdool
- Update Platform.sh @herbdool
- Update Composer @herbdool
- Update Docker @Wylbur
- Update the Wikipedia articles @klonos
Backdrop's Website updates
- backdropcms.org @jenlampton
- beta.backdropcms.org @bugfolder
- docs.backdropcms.org @jenlampton
- events.backdropcms.org @jenlampton
- forum.backdropcms.org @jenlampton
- localize.backdropcms.org @jenlampton
See Also
Reactions are currently unavailable