Project present and future

Key features in version 1.20

Release date: Sept 15th, 2021

Backdrop 1.20 (release notes); includes a shiny new Telemetry module that will allow the core developers to better evaluate what features to add, based on what most current Backdrop sites are actively using. Other new features include:

  1. new Telemetry module in core
  2. Dismissible messages
  3. Better taxonomy permissions
  4. Support for the HTML5 details element
See the GitHub issue tracker for all 1.20 issues.

Features planned for version 1.21

Scheduled release date: January 15th, 2022

  1. Advanced Caching (a.k.a. cache tags and cache max-age)
  2. Save Draft (module) in core
  3. More TBD!
See the GitHub issue tracker for 1.20 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

  1. A more intuitive administrative interface with every release.
  2. Improved the out-of-the-box Experience.
  3. Ensure that a transition from Drupal 7 is as smooth as possible.
  4. More TBD!

Specific Goals

  1. Automatic core updates (push-button core updates have been available since 1.11).
  2. A flexible reference field for content, user accounts, etc.
  3. Improved multilingual support (especially for RTL languages).
  4. More TBD!

Goals for 2.0

Backdrop 2.0 will NOT be released before January 15th, 2025.

Backdrop Version 1 will continue to be the active branch of development until at least 2024. Development will continue on version 1 for at least 2 years after Drupal 7's end-of-life in November 2022. 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.

The upgrade from Backdrop 1 to Backdrop 2 will be easier than the upgrade from Drupal 7 to Backdrop CMS, which is already easier than the upgrade from Drupal 7 to Drupal 8.

See the GitHub issue tracker for more 2.x issues for a set of proposed changes that cannot happen during the 1.x cycle.