"We'll ship it next quarter" is basically the national anthem of the software industry, and Drupal core just belted out its own verse. The good news: unlike most projects that go quiet after a missed date, Drupal actually told everyone exactly what happens next.
The Second Deadline Drupal Also Didn't Make
Drupal core built three shots at a Drupal 12.0.0 release right into its 2026 schedule: June, August, or December, each one a fallback for the last. The project already missed the June window, then missed the week-of-August-10 target too, after maintainers determined a batch of critical requirements wouldn't be ready in time — among them PHPUnit 12 support, a new JavaScript import maps API, admin theme updates, and an ESLint 9 migration.
The third and final window is now locked in: the week of December 7, 2026, contingent on beta-critical requirements landing by September 11. Beta1 is targeted for mid-September, with release candidates expected in November. If that date slips too, there's no fourth window waiting in the wings.
Why a Slipped Date Is Actually the Boring, Good Kind of News
Here's the part worth appreciating: Drupal core doesn't ship on vibes or hype-cycle timelines. It ships on a public schedule with fallback windows built in specifically so a missed date means "see you at the next scheduled stop" instead of radio silence for a year while everyone speculates. Compare that to the frameworks that just quietly go dark.
For anyone running a Drupal site, this is genuinely useful information, not just trivia. It buys more runway before Drupal 10 support winds down, since that end-of-life date is tied to the same schedule, and it gives you a real, load-bearing date to plan a migration budget around instead of a moving target you have to keep refreshing the blog to track.
A deadline that gets pushed with a public explanation and a firm next date beats a deadline that just quietly evaporates — every time.
If your team's been putting off a Drupal 12 readiness plan because the date kept moving, now's actually the right moment to start — let's map out your migration timeline.
Source: Drupal.org