Backdrop core developers and project leaders are frequently called upon to make important development decisions, with very little information about how site owners and administrators typically use Backdrop CMS and how they configure it. With the release of Backdrop 1.20.0 (and later versions), we hope that situation is getting better, but we need your help.
Here you'll find posts about both the software and the Backdrop community.
There is a preview release available for Backdrop 1.21.0. Please use this version if you would like to help us test the features in the new version of Backdrop prior to the official release on January 15th, 2022.
Please, consider spinning up a new site or testing this preview release on a test site to help us catch any new bugs or regressions.
Notes for updating
Backdrop CMS is about 45 days away from our 22nd on-time release, version 1.21.0. Every 4 months, we release a new version which brings with it new improvements and features to Backdrop CMS. Feature freeze is scheduled for January 1, 2022 and the release will be on Jan 15th. In the final weeks of each release cycle, there is a frenzy of activity and we try to get new improvements finalized and approved.
We are very close to merging (this PR has now been merged) a pull request into the 1.20 branch of Backdrop CMS that will make it possible to create simple recipes in the form of modules with nothing but a .info file and a batch of config files. While not trivial to create, these "recipe" modules could in theory be downloaded from BackdropCMS.org, installed through the UI, and enabled just like any other module.
Please, join us for the next Backdrop LIVE - taking place on July 9-10 (or 11th, depending upon your time zone). This is a great chance to learn about Backdrop CMS, meet the Backdrop community, ask questions, and help plan for the future.
We've made a change in how we schedule our weekly development, outreach, and design/ux meetings to better accommodate our international participants. Participants in the southern hemisphere were experiencing 4 time changes per year due to daylight savings with a total swing of 2 hours, while participants in the USA experienced consistent start times all year.
When I was first approached about being a Backdrop CMS core committer, I was both humbled and more than a little scared. I'm extremely grateful to the PMC for having the confidence in me to offer me this role in the community, but the amount of responsibility they were handing over made me a bit hesitant. Could I do this? What if I made mistakes? What did they expect of me time-wise? This article aims to pull back the curtain and show how easy (and rewarding) it is to be a Backdrop core committer.