With the help of a few key community members, we have been hard at work creating an interface for users to attribute their work in the issue queues to a customer or employer. (#2288727: [meta] Provide credit to organizations / customers who contribute to Drupal issues)
It’s time for another community spotlight, and this month, we’re highlighting a community member who has made huge contributions to the success of the Drupal project and of DrupalCon — and not only through code.
Now the new year has started, it's time for our community to think about the future. It has become a tradition for for years now to predict what the year ahead will bring for us -- so share your thoughts!
Happy birthday to Drupal! On this day in 2001, Drupal 1.0 was released.
On October 29, the Drupal Security Team issued a Public Service Announcement (PSA) as a follow-up to Security Advisory SA-CORE-2014-005, which disclosed a serious SQL Injection vulnerability in Drupal 7. Our goals with the PSA were to:
Update: Drupal 7.35 and Drupal 6.35 are now available.
Drupal 7.34 and Drupal 6.34, maintenance releases which contain fixes for security vulnerabilities, are now available for download. See the Drupal 7.34 and Drupal 6.34 release notes for further information.
Upgrading your existing Drupal 7 and 6 sites is strongly recommended. There are no new features or non-security-related bug fixes in these releases. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement. More information on the Drupal 6.x release series can be found in the Drupal 6.0 release announcement.
Update: Drupal 7.34 is now available.
Drupal 7.33, a maintenance release with numerous bug fixes (no security fixes) is now available for download. See the Drupal 7.33 release notes for a full listing.
Upgrading your existing Drupal 7 sites is recommended. There are no major new features in this release. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement.