-
Notifications
You must be signed in to change notification settings - Fork 40
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.27.0 Release checklist #6369
Comments
Release notes draft: The Backdrop community is proud to release version 1.27.0 of Backdrop CMS, following our 4-month release cycle. Backdrop 1.27.0 includes a major upgrade to CKEditor, updating from CKEditor 4 to CKEditor 5. While existing sites can continue to use CKEditor 4, it's recommended to transition to CKEditor 5 as soon as possible. CKEditor 4 is still included in Backdrop 1.27.0 and existing sites are not automatically updated. See the upgrading to CKEditor 5 blog post for more information. Another major compatibility change includes fully dropping support for Internet Explorer (all versions). Microsoft officially stopped supporting Internet Explorer in 2021. Microsoft Edge and other browsers are not affected by this change. Notes for updatingNo changes have been made to the It will be necessary to run the update script (located at Change records
New features
Bug fixes(These fixes were made between 1.27.0-preview and the 1.27.0 release.)
Miscellaneous changes
|
The events site is updated (and I updated the theme too so the newsletter signup in the footer looks nice) |
The Pantheon upstream is updated. |
The new language template file for the translation server is created. |
I tried to update the demo sandboxes but I don't seem to understand how the update process works. I think the repository is at https://github.com/backdrop-ops/tugboat-demos, but I don't know how to update it. @klonos (or @BWPanda), could you help provide some insight? |
I'm on it @quicksketch ...I usually just follow the instructions we already have in https://github.com/backdrop/backdrop-issues/wiki/Update:-Tugboat and that's all it takes. |
...all done! 😉 (checked by spinning a new demo site, and confirmed that it was provisioned with 1.27.0) Moving on to update the Wikipedia pages next... |
...I've updated the Wikipedia template, however the 2 articles where it's being used have not been updated yet. All the previous times I've done that before would also update the the 2 articles instantly. Perhaps there's some delay before the changes propagate now. I'll check again later. |
Ah thanks, I didn't think to check the wiki. Would you be willing to update the README in the tugboat-demos with a link to the wiki for future reference? @klonos |
@quicksketch there's a link to the Wiki in the respective task in the issue summary (and that's in the template we use for the release tasks, so it's always there) 😉 Wikipedia articles updates to reflect 1.27.0 btw. |
@quicksketch I don't have permissions in the tugboat-demos repo (can I please?), so here's a PR instead: backdrop-ops/tugboat-demos#7 |
Super, thanks @klonos! I made you an admin on the repository. |
Closing as outdated. |
Scheduled for January 15, 2024 4pm - 8pm PT
Pre-release tasks
Fix
orFixed
,Add
orAdded
.**Notes for updating**
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.
.htaccess
settings.php
The database update script does **not** need to be run.
**It will be necessary to run the update script** (located at /update.php) for this release.
**Changes since version 1.xx.x** are listed below.
release-notes
artifact attached to the generator.Release tasks
1.10.x
) and push to GitHub (@quicksketch)1.11.x-dev
) (@quicksketch)1.10.x-dev
) (@quicksketch)Immediate Post-release tasks
Publicity tasks
Code tasks
Backdrop Website updates
2-week Post-release tasks
These should be done after the first bug-fix release or 14 days -- whichever
comes sooner.
Publicity tasks
Backdrop Website updates
See Also
The text was updated successfully, but these errors were encountered: