Project present and future
- Version 1.31 current release (released May 15, 2025)
- Goals for Version 1.32 (scheduled for September 15, 2025)
- Goals for future 1.x releases
- Version 2.0 (not before Jan 2026)
Key features in version 1.32
Release date: May 15th, 2025
Backdrop 1.32 (release notes) new features include:
- Allow modules and themes to be enabled via config sync / import. #5163
- Increase performance with cache bin for Book navigation data #6787
-
Entity's
label()
method now uses the 'label callback' property. #6877 - Add the option to append original sort order to Views table column sort. #6708
- Add responsive behavior with settings for the existing Views grid style. #5719
- Update CKEditor5 to version 46.0.2 #6788
Features planned for version 1.33
Scheduled release date: January 15th, 2026
See the GitHub issue tracker for all 1.33 issues.
Goals for 1.x
All Backdrop 1.x releases will include new features that do not require API breaks. A subset of proposed topics are listed below. Please note: our priorities may change based on the most urgent needs of the Backdrop community.
General Goals
- A more intuitive administrative interface with every release.
- Improved the experience for those new to Backdrop CMS.
- Ensure that a transition from Drupal 7 is as smooth as possible.
- More TBD!
Specific Goals
- Automatic core updates (push-button core updates have been available since 1.11).
- Improved multilingual support (especially for RTL languages).
- More TBD!
Goals for 2.0
Backdrop 2.0 will NOT be released before January 15th, 2026.
Backdrop Version 1 will continue to be the active branch of development until at least January 15th, 2026. Backdrop version 1 will continue to be supported until Backdrop version 3 is released.
Backdrop 2.0 will include the removal of deprecated functions, and will most likely include changes in HTML markup which may require updates to themes.
The upgrade from Backdrop 1 to Backdrop 2 will be easier than the upgrade between major Drupal versions.
See the GitHub issue tracker for more 2.x issues for a set of proposed changes that cannot happen during the 1.x cycle.
See the summary of discussions that took place in early 2024.