Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backdrop 1.30.0 Release checklist #6828

Open
28 of 48 tasks
jenlampton opened this issue Jan 15, 2025 · 11 comments
Open
28 of 48 tasks

Backdrop 1.30.0 Release checklist #6828

jenlampton opened this issue Jan 15, 2025 · 11 comments
Milestone

Comments

@jenlampton
Copy link
Member

jenlampton commented Jan 15, 2025

Scheduled for January 15, 2025 1pm - 4pm 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.
  • Merge commits @herbdool
  • N/A Move all unfinished issues to the next bug-fix release milestone
  • Review all closed issues in milestone: @jenlampton
    • Issue titles should include a complete, but very brief summary of the problem.
    • Bug issue titles should start with Fix or Fixed,
    • New feature issue titles should start with Add or Added.
    • Each issue should have accurate labels, especially the "type - " labels.
  • Close the milestone
  • Draft Release notes
    • 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** are listed below.
        • 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.
        • 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

Immediate Post-release tasks

Publicity tasks

Code tasks

Backdrop Website updates

2-week Post-release tasks

Publicity tasks

See Also

@quicksketch
Copy link
Member

The bug fix release only contained 3 fixes, I went ahead and created it so we can focus on 1.30.0.

https://github.com/backdrop/backdrop/releases/tag/1.29.4

@quicksketch
Copy link
Member

Tag is cut: https://github.com/backdrop/backdrop/releases/tag/1.30.0

@herbdool
Copy link

I think anything with @klonos will need someone else to take it on. Like Tugboat.

@jenlampton
Copy link
Member Author

He was around this week - but I would also love to take those off his plate :)

@jenlampton
Copy link
Member Author

jenlampton commented Jan 15, 2025

Release notes draft:

The Backdrop community is proud to release version 1.30 of Backdrop CMS, following our 4-month release cycle. Highlights include Backup and restore functionality, Simplified login pages, and updates to the Basis theme including a new hero background.

Notes for updating

  • The settings.php file has been modified in this release to add $settings['backup_directory']. See the creating backups documentation for more information. Adding this setting is optional.
  • Changes have been made to the .htaccess file. No changes have been made to the robots.txt file in this release. Updating customized version of the .htaccess file is necessary.
  • The database update script at /core/update.php does need to be run.

Changes since version 1.29.4

New features

  • Add basic backup and restore functionality to update.php #2409
  • Streamline login pages with options for no-tabs and simplified layout #6570
  • Add a new SVG image for hero block in Basis #6752
  • Add a preview of the background image to Hero block configuration forms #6736
  • Add parent menu selector to menu add/edit link form #6390
  • Add support for supplemental CSS selectors in Basis #4782
  • Allow the "Book outline" vertical tab in the content create/edit form to be hidden #3638
  • Make position of #description (help text) configurable in Form API #1403
  • Replace the token browser with the Fast Token Browser from contrib #6143 (see change record)

API improvements

  • Switch to a simplified array syntax for database connection information in settings.php #2231 (see change record)
  • Remove unused parameter $config_name from config_uninstall_config() #6175 (see change record)
  • Make the link_field Form API element reusable within custom forms #6693
  • Add ability to track active CKEditor 5 instance #6770
  • Allow tableselect element options to be disabled #6730
  • Renamed hook_layout_info() to hook_layout_template_info() #6628

Miscellaneous changes

  • Increase minimum MySQL version to 5.5 #6724 (see change record)
  • Update CKEditor 5 to v44.1.0 #6695
  • Cleanup OpenSans webfonts and update to latest version #6728
  • Remove workaround for old MySQL bugs from schema.inc #6466
  • Improve performance in node access query building #3775
  • Add back "Maximize" button to Basic text format at install time #6382
  • Convert "Recent content" block to a View #146
  • Allow both front-end and back-end themes to use the new simplified login pages #6799

Bug fixes

  • Fixed Installer module uses deprecated ajaxComplete method #6785
  • Fixed "Backups are not available" message not visible in update script.#6801
  • Fixed error if $settings['backup_directory'] is commented out #6800
  • Fixed Fast Token Browser Update hook name #6761
  • Add #states property to link_field form element #6783
  • Ensure page is accessible by current user before using simplified display #6815

User Experience Improvements

  • Update Block module label and description #6781
  • Improve the help text on the Custom blocks page. #6531
  • Improve details element display in Seven theme for Chromium based browsers #6810
  • Fix margin/padding for messages on homepage in Basis theme #5769

@jenlampton
Copy link
Member Author

I'm re-opening/closing the milestone so I can get the release notes from the generator (and compare to above)

@herbdool
Copy link

@jenlampton I think "Make position of #description (help text) configurable in Form API" is actually a new feature, since it actually changes the default position for the description of some elements (in addition to making it configurable in the api).

@jenlampton
Copy link
Member Author

Done, and I've also added changes since the preview release into the list.

@Wylbur
Copy link
Member

Wylbur commented Jan 16, 2025

Docker image has been updated to 1.30.0 release.

@olafgrabienski
Copy link

I've created a new language template file for Backdrop 1.30.

@olafgrabienski
Copy link

Create a new language template file for the translation server ...

@jenlampton Is there a template for the release checklist somewhere? I'm asking because in the translation task there was another "olaf" mentioned. It shouldn't be @olaf but @olafgrabienski.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants