On Feb 29th, we've scheduled the first of what we expect to be a series of discussions about the future of Backdrop CMS, specifically about the idea of a 2.0 release of Backdrop CMS.
Don't Panic!
The number 1 priniciple in the Backdrop CMS philosophy is "Easier updates: Backwards compatibility is important."
No decisions have yet been made about what Backdrop 2.0 will look like, when it will happen, or what the upgrade process will look like. We know that many of our friends are still recovering from the trauma of the Drupal 7 EOL (end of life) and we are not looking to repeat that situation. But, we do need to at least start a discussion about the following kinds of questions.
- Do we need a Backdrop 2.0?
- How much change is acceptable in a 2.0 major release?
- How can we minimize the impact of a 2.0 release on the people who own and manage Backdrop CMS sites?
- Do we have a target date for a 2.0 release or how will we know when the time has come?
- What features or improvements, if any, would require a 2.0 release?
- When and how might we want to open a 2.0 development branch?
- How long after the launch of Backdrop 2.0 would we expect to support Backdrop 1.0?
- And more...
Let's start the discussion here in the forum.
What do you think?
Recent comments
Hello @NumerousHats, I agree with your assessment. I am looking into this situation right now. The root of this problem is that Backdrop CMS is implemented on top of a "stack" of...
Update Core and Theme via Web interface
I just installed a Backdrop CMS site with version 1.27.0. I then used the user interface to download and update Backdrop CMS to 1.30.0. After starting the update process, and on the...
1.30.0 update.php generates incorrect link
I believe my permissions are set up correctly, as I can install modules from the UI. But for whatever reason, I can't update them. I will, however, double check against that documentation.
Update Core and Theme via Web interface
I'm not sure if this is helpful, but here are pages in Backdrop documentaion about server level permissions. https://docs.backdropcms.org/documentation/file-permissions-and-ownership...
Update Core and Theme via Web interface
Just ran into this issue while upgrading modules on a site I'm setting up. I'm confused. Does this mean that /modules needs to be owned by www-data? (Not just that www-data...
Update Core and Theme via Web interface