Update: Drupal 7.15 and Drupal 6.27 are now available.

Drupal 7.14 is now available, which contains bug fixes as well as fixes for security vulnerabilities from Drupal 7.13.

Drupal 6.26, which fixes known bugs (no security issues) is also available for download.

Upgrading your existing Drupal 7 and 6 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, more information on the 6.x releases can be found in the Drupal 6.0 release announcement. Drupal 5 is no longer maintained, upgrading to Drupal 7 is recommended.

Changelog

Drupal 7.13 only includes fixes for security issues. Drupal 7.14 also includes bugfixes. The full list of changes between the 7.12 and 7.14 releases can be found by reading the 7.14 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log.

Drupal 6.26 only includes bugfixes.

Security vulnerabilities

Drupal 7.13 were released in response to the discovery of security vulnerabilities. Details can be found in the official security advisory:

• SA-CORE-2012-002

To fix the security problems, please upgrade to Drupal 7.13.

What is included with each release?

We made two versions of Drupal 7 available, so you can choose to only include security fixes (Drupal 7.13) or security fixes and bugfixes (Drupal 7.14). You can choose your preferred version. We are trying to make it easier and quicker to roll out security updates by making security-only releases available as well as ones with bugfixes included. We hope this helps you roll out the fixes as soon as possible. Read more details in the handbook.

Known issues

- #1558548: Notice: Undefined index: default_image in image_field_prepare_view() – Upgrading from Drupal 7.x to Drupal 7.14 will yield a harmless but annoying PHP notice. Patch has been committed to 7.x-dev, and will be available in 7.15. A workaround in the meantime is visiting the field settings page and saving.
- #1541792: Enable dynamic allowed list values function with additional context – This issue introduced an more context to hook_options_list(). However, because Entity API was calling this hook directly it causes errors such as Warning: Missing argument 2 for taxonomy_options_list() in taxonomy_options_list() (line 1375 of modules/taxonomy/taxonomy.module).. Fixed in Entity API module at #1556192: Incorrect invocation of hook_options_list().
- #1171866: Enforced fetching of fields/columns in lowercase breaks third-party integration – This issue accidentally introduced an API change that affected both Migrate and Backup and Migrate modules. Solution for Migrate is to rename tables in scripts back to their proper names. Solution for Backup and Migrate is at #1576812: Could not complete the backup.
- #811542: Regression: Required radios throw illegal choice error when none selected
- #1571104: Can’t access non-node entities with EntityFieldQuery

We are thrilled to announce that Google will be sponsoring 13 Drupal projects for Summer of Code 2012. We would like to extend our sincere thanks to Google, who are investing over $72,000 in the Drupal project.
As always, we had many more projects tha…

Back in 2009, Groups.Drupal.Org (GDO) went through a major transition including upgrading from Drupal 5 to Drupal 6, a redesign, and adding new maintainers. We are currently in the process of a similar transition. The site has already gone through a redesign, and as we make plans to transition to Drupal 7, we will also be moving to new maintainers for the next year.

Making it easier to contribute to GDO

Between the Drupal Association’s initiative to improve *.drupal.org, the community brainstorming on site improvements, and feature requests in the Groups.Drupal.Org issue queue, there is clearly a lot of interest in making improvements to GDO. However, for folks who want to roll up their sleeves and help by filing a patch, the path to replicating GDO for development purposes hasn’t always been clear. As a strategy for making it easier for anyone in the Drupal community to file a patch and streamlining maintenance efforts for the site, we have proposed that GDO will run the Commons distribution of Drupal for Drupal 7. Of course, this means that improvements made to GDO benefit sites powered by Drupal Commons and vice-versa, that generic improvements to Commons will benefit GDO.

New maintainers: Meet Ezra, Scott, and Justin

Helping with this transition, Ezra Gildesgame (ezra-g), maintainer of Drupal Commons, is also now a maintainer of groups.drupal.org. Ezra is the technical lead for Drupal distributions at Acquia, has been contributing to Drupal for over 5 years, and also maintains the Conference Organizing Distribution (COD).

Our other new Groups.Drupal.Org maintainers are Scott Reynen (sreynen) and Justin Toupin (justin2pin) from Aten Design Group. Scott is Lead Developer at Aten and has been contributing to Drupal for over 5 years, including helping to organize the Denver group on GDO. Justin Toupin is CEO at Aten, and has been leading the organization’s involvement in Drupal since version 4.7.

Getting involved: How you can make GDO better

This process of upgrading Groups.Drupal.Org is an especially good time to get involved by joining a few different groups and queues:

• Commons related are the Commons group, and the Commons issue queue for bugs/ideas that affect all Commons sites.
• The GDO issue queue is for features and tasks specific to Groups.Drupal.Org.
• Groups to discuss the site: http://groups.drupal.org/maintenance and http://groups.drupal.org/groups-drupal-org

Note that Ezra, Scott, and Justin have agreed to work on the site for at least a year. If you think you might want to take over in a year, the best way to do that is to get involved working on the site in these issue queues.

Thanks, Greg & Josh!

This is also a great opportunity to thank Greg Knaddison (greggles) and Josh Koenig for their help maintaining Groups.Drupal.Org over the past few years. Josh and Greg found they were too busy with other projects unrelated to community site building which made it harder to find time for GDO (Josh building Pantheon and Greg working with Acquia’s Profesional Services Security Group and the Drupal Security Team). Greg and Josh hope that transitioning to people who spend more of their lives working on community sites will help GDO be an even more valuable collaboration platform for our community.

Some of Drupal’s Summer of Code success stories include:

Angela Byron (webchick) the Drupal 7 co-maintainer, Director of Community Development at Acquia, a Google-O’Reilly Open Source Hall of Famer and a Drupal Association board member. She originally got her start in Drupal writing Quiz module for GSoC 2005.	Sumit Kataria, started as a GSoC student back in 2009 working on OAuth module, and now not only is one of the foremost experts in the Drupal community on mobile (look for his mobile apps for DrupalCon Denver in an app store near you!), but co-manages Drupal’s involvement in GSoC. He works as a Drupal consultant with companies like CivicActions and Lullabot.
Bojan Zivanovic (bojanz) became a preeminent contributor to views and contributed to EntityFieldQuery for Drupal 7.	Gábor Hojtsy, the co-maintainer of Drupal 6, and the Initiative Lead for the Drupal 8 Multilingual Initiative worked over GSoC in 2006 to get i18n in Drupal core in Drupal 6. He is now an engineer for Acquia.
Jimmy Berry (boombatower) was instrumental in the development of Drupal’s automated testing framework, and he and his father Jim Berry (solotandem) were the first Google Summer of Code father/son team! They both offer testing-related services at http://boombatower.com.	Lin Clark (linclark) created SPARQL Views, making it possible to query SPARQL endpoints from Views, as part of GSoC 2010. Her demonstrations of Linked Data capabilities in Drupal have been published on IBM Developer Works. She is now an independent consultant working data publishing and consumption using Drupal.

So if you’re:

• a post-secondary student looking for an exciting project with a thriving development community and tons of smart people you can work with
• an existing Drupal contributor who happens to be attending college/university and would love a chance to get paid over the summer to work on the “Next Big Drupal Thing”
• a seasoned Drupal developer with some time over the summer, who’d truly enjoy mentoring and helping the next generation of contributors make Drupal the best that it can be
• a Drupal community member who might not have the time or coding experience to mentor, but knows where to find resources and enjoys helping others find them.
• someone with a great project idea for an improvement in Drupal that would be perfect for a student to work on over the summer
• a Drupal evangelist who wants to help grow the community by actively engaging students

…then there’s something for you in Summer of Code! Read on to find out more.

Prospective Students

If you have enthusiasm the drive to work on something great, now is the time for you to get started! Subscribe to the Google Summer of Code group, look over the developer’s guide and API reference, stop by Core Office hours and take on some new contributor tasks, find a Drupal event near you to get to know Drupal’s amazing community, and take on a few bite-sized tasks in the Novice Issue Queue.

Most importantly, start thinking about your project proposal! Prior to submitting your application, stop by #drupal on irc.freenode.net or post your project ideas to the Summer of Code 2012 group to get community feedback. Your chances of getting into Summer of Code increase if the community has the opportunity to review your ideas and offer feedback to help you in improving your project idea.

We have already started accepting applications. For more tips, students should check out the Student Template Page.

Mentors

Please sign up to be a mentor if you have either experience with Drupal development or expertise in a particular area of interest (for example, newspapers, education…) and have some free time from now until the end of August.

To become a mentor,  join the Drupal SoC-2012 group and the sign up on Google’s SoC mentor web app (now known as Melange). Please describe who you are, what your level of Drupal experience is, and your motivation for being a mentor. Your application will be reviewed by SoC admins (Chx, SumitK).

You can go through Advice for mentors page to find more tips on mentoring students.

The more mentors we have, the more students we can get in, and the more exciting projects of varying types we can accept.

Community members

Great project ideas are vital to attracting both great students and great mentors. If you’ve ever thought “if Drupal could be…”, now is the time to turn it into a project idea. The project should be feasible for a Drupal-novice developer student to achieve in a 3-month time frame. Suggest a SoC project idea in the SoC 2012 group or help elaborating already proposed ideas

In addition, you can help review the existing SoC project ideas by providing students and other community members with feedback. Community members are in the best position to help students understand the finer intricacies of existing modules, and help their energies to meet the the priorities of the Drupal project.

To help the new Drupal family members, we need some existing community members to be active in #drupal-contribute on irc.freenode.net to answer student questions, point them to the correct resources, and people with expertise.

If you think this sounds like fun, be sure to get on to IRC!

As the Documentation Team lead, Jennifer “jhodgdon” Hodgdon has done a fantastic job of not only keeping Drupal core’s API documentation high-quality and consistent, but also of on-boarding new Drupal core contributors through the “Novice” issue queue….