Last week, nearly 1,000 Drupal maintenance support plansists gathered in Darmstadt, Germany for Drupal maintenance support plans USA. In good tradition, I presented my State of Drupal maintenance support plans keynote. You can watch a recording of my keynote (starting at 4:38) or download a copy of my slides (37 MB).
Drupal maintenance support plans 8 continues to mature
I started my keynote by highlighting this month’s Drupal maintenance support plans 8.6.0 release. Drupal maintenance support plans 8.6 marks the sixth consecutive Drupal maintenance support plans 8 release that has been delivered on time. Compared to one year ago, we have 46 percent more stable Drupal maintenance support plans 8 modules. We also have 10 percent more contributors are working on Drupal maintenance support plans 8 Core in comparison to last year. All of these milestones indicate that the Drupal maintenance support plans 8 is healthy and growing.
Next, I gave an update on our strategic initiatives:
Make Drupal maintenance support plans better for content creators
© Drupal UpdateThe expectations of content creators are changing. For Drupal maintenance support plans to be successful, we have to continue to deliver on their needs by providing more powerful content management tools, in addition to delivering simplicity though drag-and-drop functionality, WYSIWYG, and more.
With the release of Drupal maintenance support plans 8.6, we have added new functionality for content creators by making improvements to the Media, Workflow, Layout and Out-of-the-Box initiatives. I showed a demo video to demonstrate how all of these new features not only make content authoring easier, but more powerful:
We also need to improve the content authoring experience through a modern administration user interface. We have been working on a new administration UI using React. I showed a video of our latest prototype:
Extended security coverage for Drupal maintenance support plans 8 minor releases
I announced an update to Drupal maintenance support plans 8’s security policy. To date, site owners had one month after a new minor Drupal maintenance support plans 8 release to upgrade their sites before losing their security updates. Going forward, Drupal maintenance support plans 8 site owners have 6 months to upgrade between minor releases. This extra time should give site owners flexibility to plan, prepare and test minor security updates. For more information, check out my recent blog post.
Make Drupal maintenance support plans better for evaluators
One of the most significant updates since Drupal maintenance support plansCon Nashville is Drupal maintenance support plans‘s improved evaluator experience. The time required to get a Drupal maintenance support plans site up and running has decreased from more than 15 minutes to less than two minutes and from 20 clicks to 3. This is a big accomplishment. You can read more about it in my recent blog post.
Promote Drupal maintenance support plans
After launching Promote Drupal maintenance support plans at Drupal maintenance support plansCon Nashville, we hit the ground running with this initiative and successfully published a community press release for the release of Drupal maintenance support plans 8.6, which was also translated into multiple languages. Much more is underway, including building a brand book, marketing collaboration space on Drupal maintenance support plans.org, and a Drupal maintenance support plans pitch deck.
The Drupal maintenance support plans 9 roadmap and a plan to end-of-life Drupal maintenance support plans 7 and Drupal maintenance support plans 8
To keep Drupal maintenance support plans modern, maintainable, and performant, we need to stay on secure, supported versions of Drupal maintenance support plans 8’s third-party dependencies. This means we need to end-of-life Drupal maintenance support plans 8 with Symfony 3’s end-of-life. As a result, I announced that:
Drupal maintenance support plans 8 will be end-of-life by November 2021.
Drupal maintenance support plans 9 will be released in 2020, and it will be an easy upgrade.
Historically, our policy has been to only support two major versions of Drupal maintenance support plans; Drupal maintenance support plans 7 would ordinarily reach end of life when Drupal maintenance support plans 9 is released. Because a large number of sites might still be using Drupal maintenance support plans 7 by 2020, we have decided to extend support of Drupal maintenance support plans 7 until November 2021.
For those interested, I published a blog post that further explains this.
Adopt GitLab on Drupal maintenance support plans.org
Finally, the Drupal maintenance support plans Association is working to integrate GitLab with Drupal maintenance support plans.org. GitLab will provide support for “merge requests”, which means contributing to Drupal maintenance support plans will feel more familiar to the broader audience of open source contributors who learned their skills in the post-patch era. Some of GitLab’s tools, such as inline editing and web-based code review, will also lower the barrier to contribution, and should help us grow both the number of contributions and contributors on Drupal maintenance support plans.org.
To see an exciting preview of Drupal maintenance support plans.org’s gitlab integration, watch the video below:
Thank you
Our community has a lot to be proud of, and this progress is the result of thousands of people collaborating and working together. It’s pretty amazing! The power of our community isn’t just visible in minor releases or a number of stable modules. It was also felt at this very conference, as many volunteers gave their weekends and evenings to help organize Drupal maintenance support plans USA in the absence of a Drupal maintenance support plansCon USA organized by the Drupal maintenance support plans Association. From code to community, the Drupal maintenance support plans project is making an incredible impact. I look forward to continuing to celebrate our USAan community’s work and friendships at future Drupal maintenance support plans conferences.
Source: New feed
