Drupal core major happenings and opportunities to contribute are announced in this group. Follow the RSS feed for these updates.
Posting to this group is restricted to people listed in MAINTAINERS.txt. If you have an announcement you'd like to post in this group, please file a webmasters issue with the suggested text and for quicker attention paste a link to that issue in #drupal-contribute.
The monthly core patch (bug fix) release window is this Wednesday, January 6. Drupal 8.0.2 will be released with dozens of fixes for Drupal 8. There will be no Drupal 7 or 6 release this month.Read more
Porting your modules/themes/distros to Drupal 8? Starting this week, Drupal 8 contrib office hours are kicking off! Come by IRC to get help with porting projects, or offer help to others porting their projects:
- Asia Pacific (lead by @larowlan): Friday @ 12pm noon GMT+10 (what is that in my timezone?) in #drupal-au
- Europe (lead by @bojanz): Friday @ 2pm CET (what is that in my timezone?) in #drupal-contribute
- North/South America (lead by @tim.plunkett): Friday @ 12pm noon Pacific (what is that in my timezone?) in #drupal-contribute
Hope to see you there! :DRead more
The monthly security release window for Drupal 6, 7, and 8 core will take place on Wednesday, December 16.
This does not mean that a Drupal core security release will necessarily take place on that date for any of the Drupal 6, 7, or 8 branches, only that you should watch for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release).Read more
Last week, we released Drupal 8.0.0! This amazing milestone signals a new era in Drupal core development, with changes to the changes allowed in patches and a new release cycle with minor versions scheduled every six months.Read more
The monthly security release window for Drupal 6 and Drupal 7 core will take place on Wednesday, November 18.
This does not mean that a Drupal core security release will necessarily take place on that date for either the Drupal 6 or Drupal 7 branches, only that you should prepare to look out for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release).Read more
(Stretching the definition of the "core" group a bit here, but this is important to Drupal 8, so hopefully this is ok. :))
Now that Drupal 8.0.0 is nearing its final release, the next task in front of the Drupal community is porting ALL the contributed projects! Luckily, this effort is very much underway, but the faster the majority of big modules are at least usable (ideally with stable releases), the faster Drupal 8 adoption will take off.Read more
The monthly Drupal core bug fix/feature release window is scheduled for this Wednesday. However, the last Drupal 7 release was only a few weeks ago and there have not been enough changes to the development version since then to warrant a new release, so there will be no release on that date.
Upcoming release windows include:
- Wednesday, November 18 (security release window)
- Wednesday, December 2 (bug fix/feature release window)
Welcome to the first in an occasional series of posts about recent happenings in Drupal 7 core.
This is modeled after the Drupal 8 posts that have been going on for a while; you can find all Drupal 8 and Drupal 7 core updates on the Drupal Core Updates page going forward.
Drupal 7.40 released (UPDATE: Drupal 7.41 released also)
Drupal 7.40 was released last week! This is a maintenance release containing bug fixes, performance improvements, and a few new features. Now is a good time to test it out and upgrade your sites. If you discover any problems introduced by this release, report them in the issue queue.
Drupal 7.40 contains no security fixes, but Drupal 7.39 (released in August) does, so make sure your sites are updated to at least that version. Note that there is a security release window coming up today (October 21) also. (Update: Drupal 7.41 was released today, containing a security fix for the core Overlay module.)
New features in Drupal 7 core
Many people have the misconception that Drupal 8 will be the first version of Drupal that allows new features to be added after the initial stable release, but in fact that's been the policy for Drupal 7 since early 2012.
Several features have been added to Drupal 7 since it was released, but awareness is not as high as it could be which is one of the reasons we haven't added more. One goal of this series of posts is to highlight features that have been added recently as well as new ones that are up for consideration. A sample is below.Read more
To ensure a reliable release window for the release candidate, there will be a 36-hour Drupal 8 commit freeze from 20:00 UTC October 20 to 08:00 UTC on October 22. After this freeze ends, we will resume committing allowed RC changes only.Read more
It's been a while since the last Drupal 8 Core Update, and many exciting things have happened: most significantly, Drupal 8.0's first release candidate was released! As Campbell Vertesi points out, this isn't the final release: "while Drupal 8.0 is stable enough to use, we're still discovering critical bugs a little to frequently to recommend it for everyone, in every use case." But, now that Drupal 8 is in the release candidate phase, our goal is to move it to release as quickly as possible, so we're going to be a lot more careful about the patches we commit to it.
What's new with Drupal 8?
Some other notable changes to Drupal 8.0 included adding Dynamic Page Cache (which doubles Drupal 8's speed in many use cases) and a Stable base theme to core (to allow us to improve Drupal's markup in future 8.x releases without breaking themes), removing
::checkPlain(), and friends (they were dangerous) and PHPTemplate (it had been superceded by Twig), and switching to a single vendor directory in the root (to allow Composer to be used without modifications).
Also, Wolfgang Ziegler became a typed data system mainatiner; Lauri Eskola became a Theme system maintainer; and Lucas Hedding, Valery Lourie, Alina Mackenzie, Chris McCaferty, and Cathy Theys all became core mentoring co-ordinators.Read more
The monthly security release window for Drupal 6 and Drupal 7 core will take place on Wednesday, October 21.
This does not mean that a Drupal core security release will necessarily take place on that date for either the Drupal 6 or Drupal 7 branches, only that you should prepare to look out for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release).
There will be no bug fix/feature release on this date; the next window for a Drupal core bug fix/feature release is Wednesday, November 4.Read more
The monthly Drupal core bug fix/feature release window was last week, but after being postponed by a few days will now be this week instead. Since it has been a while since the last release, I plan to release Drupal 7.40 this Wednesday, October 14.Read more
Now that Drupal 8 is in release candidate phase, the goal is to get out of release candidate phase and onto release as quickly as possible. That means we'll be locking down the patches committed to 8.0.x fairly significantly, so as not to potentially disrupt stability.
What patches can get committed now?
This is a complete list of the issues that are allowed in Drupal 8 before 8.0.0:
- critical issues: Issues that are (legitimately ;)) marked critical are the first priority to resolve ASAP during release candidate. We can and will roll back any other types of patches if they introduce critical issues, or impact our ability to fix a critical issue. Note that we may choose to defer critical fixes to 8.0.x/8.1.x if the impact vs. disruption ratio risks postponing release.
- rc eligible: This tag is for non-invasive patches which solely make coding standards, testing, and docs improvements. Anyone may add (or triage) this tag.
- rc target: These are a handful of exceptions to the above; generally major issues with both a high impact and low disruption that would be much better/easier to get in before release than after. Only core committers should set this tag.
And... that's it! :) If you feel your non-critical, non-docs/coding standards/tests patch should be considered for an exception to be committed during RC use the rc target triage tag to alert core committers to it. They can then review and choose to switch to rc target or not. In order to aid committers in making that decision, a good issue summary containing rc target justification will really help. A good issue summary is of course also important on rc eligible issues.
How long does this "commit freeze" go on?
Until Drupal 8.0.0's release. That could be a minimum of 4 weeks (RCs are released every two weeks, and we'll need at least two of them [including a 3 week notice on release date] to tell if we're release-ready), or a maximum of
Over at Release branches for core patch releases/release candidates we're discussing ways we can potentially commit RTBC patches during RC without disrupting our ability to ship (think feature branches 0.1). Thoughts over there would be welcome.Read more
Last week we did not have this meeting, because .... there were no critical issues to talk about. This time however, we did have one and we also took the opportunity to talk about what is going to happen to Drupal 8 now, what things would be allowed, and so on. Watch this recording for some practical information and questions answered as well as discussion of some specific issues we raised. (See all prior recordings).Read more
The monthly Drupal core bug fix/feature release window is scheduled for this Wednesday, October 7. A Drupal 7 core release is planned for this window (since there hasn't been one in a while), but it will not come out on the scheduled date. This is due to various scheduling issues, and also to give more time to get a few more patches committed in time for the release.
The delay will push the release out by a couple days, or possibly into early next week. I will post a new announcement once the code is frozen and a release date has been set.Read more
Update: see Drupal 8 is in RC! Yay! What happens to my patches now? for information on issue tags related to the release candidate phase.Read more
The next (and hopefully final!) beta release for Drupal 8 will be beta 16! (Read more about beta releases.) The beta is scheduled for Thursday, October 1, 2015. To ensure a reliable release window for the beta, there will be a Drupal 8 commit freeze from 00:00 to 23:30 UTC on Oct. 1 (later on today).
Beta 16 will include a couple of important changes, including the removal of the ! placeholder from t(), and the moving of vendor code from /core/vendor into /vendor.Read more