Drupal 10 release windows
Our release schedule includes three potential release dates for Drupal 10.0.0, depending on when critical requirements are completed:
June 15, 2022, if key requirements are completed by March 11
August 17, 2022, if key requirements are completed by May 13
December 14, 2022, if key requirements are completed by September 9
Our new target release date for Drupal 10.0.0 is August 17, 2022
With about two weeks remaining until the March deadline, we are confident that the critical requirements will not be completed by that date. Therefore, we are officially announcing that our new target release date for Drupal 10.0.0 is August 17, 2022, and the beta deadline for critical requirements is May 13, 2022.
We need your help to complete requirements by May 13!
The community has already done an amazing job preparing for Drupal 10. Many key Drupal 10 release requirements are complete!
That said, there is still a lot more to do! Even with three months remaining until the May deadline for Drupal 10’s beta requirements, we need your help to make an August release possible.
There are also numerous pending improvements that are not hard requirements for Drupal 10’s release, but that are still critically important to its long-term support and maintainability.
See the list below for the most urgent needs.
Stabilize CKEditor 5 and deprecate CKEditor 4
The most significant change in Drupal 10 is probably the upgraded WYSIWYG editor. Drupal 8 and 9 core both integrated with CKEditor 4, which will be end-of-life at the end of 2023. We must upgrade to CKEditor 5 for Drupal 10 to receive security coverage beyond 2023.
Numerous contributors have been collaborating with CKSource for more than a year to create a new beta-stability experimental module integrating CKEditor 5 with Drupal 9. There is still a significant amount of work remaining to make it stable. After the module is stable, CKEditor 4 will also need to be decoupled from other core modules, deprecated, and moved back to contrib.
First, we need to address several known security vulnerabilities in the development dependencies. The meta issue for this is.
Then, our development dependencies should all be updated to the latest major versions in Drupal 9.4.x and 10.0.x. (See.)
Make Olivero the default frontend theme of the Standard profile, and deprecate Bartik
The new Olivero frontend theme for Drupal core has had great community momentum, and is already available as a stable theme in Drupal 9.3. The next step is to make it the default theme of the Standard profile. This will make Drupal look like the modern platform it is and will improve the evaluator experience. It will also allow us to deprecate Bartik and move it into contrib, which will improve core’s maintainability.
Make Claro the default administration theme of the Standard profile, and deprecate Seven
Claro is a beautiful, accessible, modern administration theme that greatly improves Drupal’s administrative user experience. It’s been available as a beta experimental theme in core for several years now, and it is already used on many sites. Only a few critical bugs remain to make it stable.
Once Claro is marked stable, additional work is needed to make it the default administration theme of the Standard profile, which will give Drupal 10 a fresh new look. Finally, once Claro is in the Standard profile, Seven can be deprecated and removed from core for better core maintainability.
We could use your help on all these issues!
Test and stabilize the experimental Theme Starterkit so that legacy base themes can be removed from core
The new experimental Theme Starterkit is a tool for generating new themes. It will allow us to provide an experience that more closely matches theme developer workflows, because we will be able to introduce incremental improvements to the theme. Once Starterkit is stable, we can remove both Classy and the Drupal 8 version of the Stable base theme from core.
Additionally, if we fix, core can do away with the stable base themes entirely. This will allow us to simplify core process for markup bug fixes and deliver more markup improvements in minor releases, improving the core theming experience for core maintainers, contributors, and site owners alike.
Yes, absolutely! The categories above need help the most urgently, but there are many other critical issues of all sorts that need to be completed before the May deadline. Join the #d10readiness channel in the Drupal community Slack for help finding Drupal 10 issues that fit your skillset.