September 7th has passed and the Drupal 7 code freeze is officially on. 82 weeks of development that started in February 2008 has come and gone and now it's time to relax.
So what happens during code slush time? Well you can still submit patches, for the most part. If your patch includes new functionality or features, you may be out of luck.
There are, however, ten exception categories to this "no new features and functionality" rule:
- Image Field
- Translatable fields
- Convert Profile module to Field API
- Convert Taxonomy module to Field API
- Admin overlays
- Edit anywhere
- Customizable shortcut bar
- Administrative dashboard
- Plugin Manager (automated module updates)
In addition to these, other exceptions to the code freeze include patches for:
- API changes to existing functionality that are "important and necessary"
- Improvements to usability and accessibility
- Improvements to Performance
- Improvements to Documentation
You are still looking at an October 15th deadline, so if you haven't started upgrading and testing, what are you waiting for?
The #D7CX Movement
We told you this wasn't the time to sit back and relax. With such anticipation of Drupal 7, you don't want to see down faces when people upgrade only to find out that their favorite modules aren't compatible.
That's what the D7CX Movement is about. D7CX, Drupal 7 Contributed Modules, is an initiative to have at a minimum the top 40 contributed Drupal modules be Drupal 7 ready by the time it's released. Apparently this did not happen for Drupal 6 and things didn't go so well.
Other Ways to Help Out
If you aren't working on a Drupal 7 version of your module, there are lots of other ways to help out including usability, accessibility, API clean-ups, testing framework improvements and more.
Get all the details you need on the Drupal Code Slush here.