Start: 
2014-05-07 (All day) - 2014-05-08 (All day) America/New_York

User group meeting

Organizers: 

David_Rothstein

The monthly Drupal core bug fix release window is this Wednesday, and since it has been a while since the last one, I plan to release Drupal 7.28 on that date. However, in practice the release might not happen until Thursday, to give people a bit more time to test the latest code. Per our release policy, this will be a bug fix release only (no security fixes).

The final patches for 7.28 have been committed and the code is frozen (excluding documentation fixes and fixes for any regressions that may be found in the next couple days). So, now is a wonderful time to update your development/staging servers to the latest 7.x code and help us catch any regressions in advance.

Drupal 7.28 does not have any new features or API changes that are large enough to warrant an official change record, but there are numerous significant improvements, including:

• A fix for a JavaScript regression in older browsers (typically Internet Explorer 8 and earlier) that was accidentally introduced in the Drupal 7.27 security release.
• A change which should make the Update Manager module more reliable about reporting correct information about security updates to site administrators. This change has some possible performance implications though, so we're particularly interested in any testing and feedback on the drupal.org issue: "No available releases found" - fetching update information exceeds timeout.

You might also be interested in the tentative CHANGELOG.txt for Drupal 7.28 and the corresponding list of important issues that will be highlighted in the Drupal 7.28 release notes.

If you do find any regressions, please report them in the issue queue. Thanks!

Upcoming release windows after this week include:

• Wednesday, May 21 (security release window)
• Wednesday, June 4 (bug fix release window)

For more information on Drupal core release windows, see the documentation on release timing and security releases, and the discussion that led to this policy being implemented.