After some 82 weeks of development beginning in February 2008, no one should be caught by surprise that we are near a code freeze for a release of Drupal 7, the next and best release of Drupal yet. In fact, the Drupal 7 code freeze was originally announced to be on September 1st.

However, as we all know, some of the best patches always happen at the last minute, and there are always last-minute patches that must happen. As part of my State of Drupal presentation at DrupalCon Paris today, I talked about the Drupal 7 code freeze. Since not all of us can be at Paris (and for those that aren't there, we miss you!), I wanted to share the relevant slides (PDF, 85 KB) in this blog post.

Important to know is that I extended the code freeze to Monday, September 7th. At this point all patches are still "acceptable". After the end of DrupalCon Paris, Angela "webchick" Byron and I will review everything that is marked "ready to be committed" and commit all those patches that are really ready.

After this one week extension, we enter a phase we're calling "code slush", to be time-boxed at a strict five weeks. In this period, most patches are allowed, except those that implement new features or functionality -- with some very important exceptions. Up to ten carefully selected exceptions for new functionality (see slides for details), patches that implement important and necessary API changes for existing functionality, and patches that improve usability, accessibility, documentation, and performance will still be accepted. As such, it is important that you start upgrading your contributed modules as soon as possible -- you never know what API issues you might run into and we only have a limited window to address those. After October 15, we will become a lot more strict and focus on the final polish.

As always, Drupal 7 will be ready when it's ready, but not before. We expect -- and hope -- that our huge investment in SimpleTest tests and our automated testing platform, though, will make this the easiest transition from development to release yet. We'll see!

Drupal code freeze plan


sun (not verified):

Extracting the list of exceptions for quicker lookup:

  1. Imagefield
  2. Field translations
  3. Convert profile module to field API
  4. Convert taxonomy to field API
  5. Overlays
  6. Edit anywhere
  7. Shortcuts
  8. Dashboard
  9. Plugin manager
  10. RDF/RFDa

We also have almost ready patches for converting blocks and comments to field API. In general, I don't think that all of these "Convert xyz to field API" really belong into a list of exceptions. Like Token in core (which is not being implemented at all yet), new features/APIs should be introduced in a complete and consistent fashion, as outlined in my post about the necessity of a Drupal feature freeze.

In general, I hope that you will not be so strict about this Monday's code-freeze deadline, because we all had to travel home from DrupalCon, having new clues about the importance of various not yet existing features and functionality, and there was only a time-frame of about 24 hours to quickly step back, order features/API changes by personal priority, writing patches, getting and providing peer-reviews (while only a few people were available in IRC), and trying to get at least something done (RTBC).

Therefore, many further patches went RTBC in the night from Monday to Tuesday, and I think we should take those special circumstances into account.

Thanks :)

dodazzi (not verified):

Why this crucial decision for the drupal community hasn't been published in the frontpage? That's the main source of news for many of us! Or I'm a missing something?

Thanks :)


You're absolutely right. I've just posted an update on

Zenko (not verified):

Thanks for the information Dries, I have been lurking the past months and keeping my eyes on D7.

Keep up the great work.