Note, April 2012: For information and updates on core office hours, see the handbook page on Core contribution mentoring.

Drupal core needs more eyes and more contributors to decrease the very high amount of unresolved issues.

We hold core "office hours" each week in #drupal on freenode.

Why office hours?

There are currently a large number of unresolved issues in the core queue, and we want to get more organised dealing with the backlog, and encourage new people to help out.

Current numbers:

• Over 2200 open bug reports against Drupal 8 and 7.
• Over 1750 open bug reports against Drupal 6.
• Over 500 patches needing review for Drupal 8 and 7.

The last time I organized a State of Drupal survey was in 2008. The results of the 2008 survey were instrumental in shaping Drupal 7 as well as directing the work of the Drupal Association on drupal.org.

Now three years later, I created a new survey. The results of this survey will guide thousands of people in the Drupal community over the next two years.

Take the State of Drupal 2011 survey now.

Drupal 7.5, a maintenance release which fixes security vulnerabilities is now available for download. Drupal 7.6 7.7 also fixes other issues reported through the bug tracking system.

Note: Drupal 7.7 is just Drupal 7.6 with a fixed VERSION string (7.6 was reporting itself as 7.5). No other changes.

Upgrading your existing Drupal 7 sites is strongly recommended. There are no new features in these releases. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement.

Drupal 7.3, a maintenance release which fixes security vulnerabilities is now available for download.

Drupal 7.4 also fixes other issues reported through the bug tracking system.

Upgrading your existing Drupal 7 sites is strongly recommended. There are no new features in these releases. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement.

Hello from Jennifer and Ariane, your friendly Drupal Documentation Team co-leads! It’s time for a quarterly update on what’s happening in the Documentation team—we've been trying out some new initiatives and working on infrastructure since our last update (April 5, 2011), and we'd like to get you up to date.

April - June events

• In April and May, Ariane tried out a new concept: picking out a few online Drupal.org documentation projects for the docs team to focus on, in the spirit of an agile "sprint" (not to be confused with a day-long let's-all-document "sprint"). April's sprint focused on 5 key Drupal 7 documentation updates, and it was quite successful: many people participated; four of the five documentation goals were completed, and lots of progress was made on the 5th (updating the core module documentation for Drupal 7). May's sprint had a bit less momentum, but many of the April contributors continued on, and some progress was made.
• Jennifer also made a developer-doc priority for April and May—to finish the theme and module Drupal 6 to 7 migration guides. This task was completed in June.

The DrupalCon London Team had the task of narrowing 341 fantastic proposals into a schedule of 60 sessions, balanced across 5 tracks: Site Building and Environment Set-up, Business and Best Practices, Code & Coders, Design, UX & Theming, and Ecosystem. You can check out the schedule now and attendees will be able to build their schedule on the DrupalCon London site by logging in later this week.

This breaks down to 5 tracks with 12 sessions each. The 6th track, Core Conversations, will also have 12 sessions slots available and DrupalCon London will be opening core conversation session proposals between 14 June and 14 July 2011, 23:59 GMT+1. Core Conversations are a place for people actively working on Drupal or Drupal.org to meet and plan the future of Drupal (Drupal 8). We will announce selected Core Conversation sessions on 22 July 2011.