Every developer has told a client "it'll be done by Friday" only to watch Friday become "next Friday," then "next month," then a philosophical concept. Drupal core just pulled the same move on itself — and for once, that's actually good news.
June Came and Went Without a 12.0
Drupal 12 was originally slotted for a release window back in June 2026, but with only days left on the clock, core maintainers confirmed the critical requirements simply wouldn't be finished in time. So the project rolled to its second scheduled window: the week of August 10, 2026, with a December 7 fallback still sitting on the shelf in case round two also runs long.
The holdup isn't glamorous, but it's real work: PHPUnit 12 compatibility, an import maps API that CKEditor 5 needs for its new installation method, database dump and update-path cleanup, trimming test files out of release packages, retiring the Toolbar module, migrating off an unsupported ESLint 8, and finishing the long-promised swap of the Claro admin theme for Gin. The main branch already runs on Symfony 8, so the foundation is modern — it's the finish carpentry that's eating the calendar.
Why a Slipped Date Beats a Shipped Mess
A missed deadline on a CMS that powers government sites, universities, and enterprise intranets is a feature, not a bug — nobody wants their site's foundation held together with "we'll patch it in 12.1." Drupal shipping late but stable is exactly the trade-off site owners should want, especially next to frameworks that ship on a fixed calendar and let users find the bugs afterward.
The part most casual observers miss: this list of blockers is also a preview of what your next upgrade project actually involves. Toolbar gone, Gin as the new default admin theme, CKEditor 5 needing an import maps setup — none of that is a "click update and walk away" migration for anyone running custom theming, legacy modules, or a heavily customized admin experience.
Three release windows and counting — Drupal 12 isn't rushing, it's rehearsing.
If your site's still riding Drupal 9 or an untouched Drupal 10 build, now's the moment to start planning the jump before 12 lands and the clock on unsupported versions starts ticking — let's talk about your upgrade path.
Source: Drupal.org