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
I finally found the PHP controle in my CPANEL and Reset the PHP to vwersion 7.3. Using this version I was able to clear the update caches but I am still unable to run update instite of the...
Update Problems
OK so looking a the results of running update.ph[ it calls for a specific version of PHP. My host company is providing a 8+ version of PHP. One now wonders if therre is a general limit on PHP...
Update Problems
I think, the user simply will not be allowed to create / edit / view node. This should not somehow affect to existing publications. Current rights and publication status have no connection.
Status of existing content after role permission removal
Thanks, that was it exactly!
Admin bar doesn't work for other site admin
Hello, Thank you for your response ! We followed the steps of the documentation, so we copied the content and the themes on backdrop en then we went to the page domain/core/...
Page not found after migration