Drupal 7 core release on Wednesday, April 1
Start:
2015-04-01 (All day) America/New_York
Online meeting (eg. IRC meeting)
Organizers:
The monthly Drupal core bug fix/feature release window is this Wednesday, April 1, and since it has been a while since the last one, I plan to release Drupal 7.36 on that date.
The final patches for 7.36 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.
There are three relevant change records for Drupal 7.36 which are listed below. This is not the full list of changes, rather only a list of notable API additions and other changes that might affect a number of other modules, so it's a good place to start looking for any problems:
- Added new form API functionality to prevent arrays from being submitted to text-like fields
- Added methods to avoid loading jQuery and related JavaScript libraries on all pages when they are not needed
- Added a user_has_role() API function to check if a user has a certain role
You might also be interested in the tentative CHANGELOG.txt for Drupal 7.36 and the corresponding list of important issues that will be highlighted in the Drupal 7.36 release notes.
If you do find any regressions, please report them in the issue queue. Thanks!
Upcoming release windows after this week include:
- Wednesday, April 15 (security release window)
- Wednesday, May 6 (bug fix/feature 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.