Subscribe to Drupal core announcements feed
Core announcement
Updated: 1 hour 31 min ago

PHP dependencies removed from git (8.1.x branch)

February 3, 2016 at 1:23pm

We've removed the Composer-managed vendor from the git repository.

There will not be any changes for people downloading Drupal 8 from drupal.org. The Drupal.org packager will add dependencies to zip and tar package.

If you're not using zip / tar files, e.g. when using a git clone, run composer install to get dependencies. See https://www.drupal.org/documentation/install/download#git for instructions.

Categories: Planet Drupal

Scott Reeves

February 3, 2016 at 9:11am

I'm pleased to announce that Scott Reeves (Cottser on Drupal.org) has accepted my invitation to become a provisional Drupal 8 committer. He will be focused on front-end and theming.

Scott has been working with Drupal for nearly 5 years, and has a strong passion around improving the theming experience of Drupal. Scott was a major force in the push for Twig and clean markup in Drupal 8 core, sharing both his technical expertise and his enthusiastic community-building to make Drupal 8's theme layer awesome. He helped lead the "Consensus Banana" initiative that solved a long-standing concern with how core provides classes and markup, and then helped add the Stable base theme so that Drupal core could provide backwards compatibility for themes in minor releases.

Scott has organized sprints and discussions at many DrupalCons, including the groundbreaking templating and performance testing sprint at DrupalCon Portland that allowed Twig to become Drupal's primary theme engine. He and others also organized a Drupal 8 Accelerate sprint on security criticals related to the theme system that were blocking Drupal 8's release, engaging novice contributors to fix the issues. Finally, Scott was previously a lead for the Drupal Core Contribution Mentoring program, mentoring dozens of other contributors on IRC, at sprints, etc. He is skilled at evaluating a problem, framing how it can be solved, and helping people solve it. In short: Scott has not only the strong technical abilities, but also the patient and supportive personality to make him an amazing fit for a core committer.

Scott's appointment as a core committer was enthusiastically endorsed from the rest of the Drupal 8 committers. Please join me in helping him feel welcome! And please also give thanks to his employer, Digital Echidna, who have agreed to partially sponsor his community time!

Categories: Planet Drupal

Looking for another Drupal 7 co-maintainer

February 3, 2016 at 9:05am

I selected David Rothstein as my co-maintainer for Drupal 7 back in May of 2012. Since then, David has done a tremendous job shepherding the Drupal 7 release, paying very careful attention to the ramifications of any given patch and allowing ample time for "real world" testing before incorporating changes into the code base, ensuring that the code powering 2% of the Internet stays stable and performant.

However, after nearly 4 years of excellent stewardship on his own, David would like to also focus on other endeavors, including Drupal 8. Now the time has come to select an additional co-maintainer for Drupal 7. While David himself has recommended some excellent candidates, I'd also like to open the call out more broadly, to see if there are others who have an inclination and interest.

The Drupal core maintainer handbook contains comprehensive documentation on everything that a release manager does. In particular, the ideal candidate has the following traits:

  • Ample experience building "real world" sites/platforms on Drupal 7, particularly high-performant sites, sites with millions of records, or other edge cases.
  • Ample experience performing detailed and thorough technical reviews of patches, being particularly mindful of their effects on existing sites.
  • Ability to communicate calmly and respectfully when critiquing code.
  • Solid knowledge of Git and the Drupal.org release process.
  • Ideally, sponsored time to work through your employer to maintain Drupal 7, particularly around the first and third Wednesdays of the month, which are the Drupal core release windows.

Please either respond here or use my contact form if you'd like to be considered as a potential Drupal 7 co-maintainer. Thank you!

Categories: Planet Drupal

Drupal 8 and 7 core release window on Wednesday, February 03, 2016

January 31, 2016 at 4:53pm
Start:  2016-02-24 00:00 - 23:30 UTC Organizers:  xjm catch David_Rothstein Event type:  Online meeting (eg. IRC meeting)

The monthly core patch (bug fix) release window is this Wednesday, February 03. Drupal 8.0.3 and 7.42 will be released with fixes for Drupal 8 and 7. There will be no Drupal 6 bugfix release this month.

To ensure a reliable release window for the patch release, there will be a Drupal 8.0.x commit freeze from 00:00 to 23:30 UTC on Wednesday, February 03. Now is a good time to update your development/staging servers to the latest 8.0.x-dev or 7.x-dev code and help us catch any regressions in advance. If you do find any regressions, please report them in the issue queue. Thanks!

To see all of the latest changes that will be included in the releases, see the 8.0.x commit log and 7.x commit log.

Other upcoming core release windows after this week include:

  • Wednesday, February 24 (security release window)
  • Wednesday, March 02 (patch release window)
  • Wednesday, April 20 (scheduled minor release)

For more information on Drupal core release windows, see the documentation on release timing and security releases, as well as the Drupal core release cycle overview.

Categories: Planet Drupal

Help finalizing Migrate at the Global Sprint Weekend

January 29, 2016 at 9:12pm

The Migrate team would like to finish up the Migrate subsystem for next month's release of Drupal 8.1.0. They've collected a number of issues for the upcoming global sprint weekend:

Global Sprint Weekend Migrate Issues

There are issues available for all levels of expertise. If you need help, the Migrate maintainers are in #drupal-migrate on irc.freenode.net as usual and are happy to answer questions.

Categories: Planet Drupal

Proposal: New release schedule for Drupal 7 core

January 29, 2016 at 4:43am

There is a discussion underway about adopting a similar release schedule for Drupal 7 that Drupal 8 is using (i.e., a six-month feature release schedule, with pseudo-semantic versioning).

This is not a major change to current policy, but it would mean that new features or other potentially disruptive patches to Drupal 7 core would be limited to two windows per year, with the corresponding releases given a round number (for example, Drupal 7.50, Drupal 7.60, etc.) to indicate their importance.

I'd like to bring the discussion to a close soon so that if we do adopt the new schedule, the first such release can be slated for April 20 (the same day as the Drupal 8.1.0 release).

If you have any feedback on this proposal, please try to comment within the next week here: https://www.drupal.org/node/2598382

Categories: Planet Drupal

Coding standards proposals for final discussion

January 22, 2016 at 9:20pm

The TWG coding standards committee is announcing two coding standards changes for final discussion. These appear to have reached a point close enough to consensus for final completion. The new process for proposing and ratifying changes is documented on the coding standards project page.

The two issues being proposed are:

These proposals will be re-evaluated during the next coding standards meeting currently scheduled for February 5th. At that point the discussion may be extended, or the policy may be dismissed or ratified and moved to the ‘update documentation’ step.

Categories: Planet Drupal

BigPipe in Drupal 8.1: please test!

January 21, 2016 at 12:45pm

Drupal 8.1 is accepting new features, and BigPipe is being proposed to be added as an experimental module to Drupal 8.1. BigPipe sends pages to clients in a way that allows browsers to show them much faster. It first sends the cacheable parts of the page, then the dynamic/uncacheable parts.

If you're interested or concerned, please give the BigPipe contributed module for Drupal 8.0.x a try, and even try to break it! The more confident we can be about its stability, the more likely it being part of Drupal 8.1 will be.

Categories: Planet Drupal

Work on Migrate UI, frontend testing, bug fixes, and more for Drupal 8.1.0

January 19, 2016 at 1:35pm

Drupal 8.1.0 will be released on April 20, 2016, so the beta phase for Drupal 8.1.x is coming up soon! We have until February 24 to make additions for Drupal 8.1.0. (After that, new additions will go toward 8.2.0 instead, which is currently planned for release in October.)

Our priorities for 8.1.x improvements are an experimental Migrate user interface, automated frontend testing, and most importantly bug and usability fixes.

Migrate user interface

Migrate is in core as an experimental module in Drupal 8.0.x, but it does not provide a user interface. The next step is to add the user interface as a core experimental module as well as fix a few important bugs, such as missing test coverage for the user interface and delaying migration entity saving for safer rollbacks.

Frontend testing

As we use more and more frontend components, we need to ensure that our frontend implementations are tested as well as we already test our backend. There were some prior steps introduced in Drupal 8 towards using Behat for frontend testing, and infrastructure support is almost ready. However there is more to do.

Bug and usability fixes

There are currently over 500 major bugs filed against Drupal 8 branches. The stability of Drupal 8 is always a top priority, so help with these major issues by helping create and test patches, as well as testing to determine if the issues are still relevant. Usability issues and contributed project blockers are also especially important.

Categories: Planet Drupal

Drupal core security release window on Wednesday, January 20, 2016

January 18, 2016 at 6:08pm
Start:  2016-01-20 (All day) America/Chicago Organizers:  catch xjm David_Rothstein Event type:  Online meeting (eg. IRC meeting)

The monthly security release window for Drupal 6, 7, and 8 core will take place on Wednesday, January 20.

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).

There will be no bug fix or feature release on this date. The next window for a Drupal core patch (bug fix) release for all branches is Wednesday, February 3, 2016. The next scheduled minor (feature) release for Drupal 8 will be on April 20, 2016. This is the second-to-last security release window before the Drupal 6 end-of-life on February 24.

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.

Categories: Planet Drupal

New Coding Standards Update Process

January 9, 2016 at 5:07pm

The Technical Working Group was rebooted about a year ago and has been working to clarify and close issues related to the technical aspect and ramping up to take on our biggest assignment: vetting, clarifying, accepting, and announcing all coding standards changes.

Historically there has been no official process for coding standards changes and these issues and the nature of them are notoriously difficult to get developers to agree on leading to endless bike-shedding and difficulty in finding complete consensus. To this end we have worked with interested community members to draft and approve a new policy for reviewing, deciding, and announcing new coding standards changes. To that end we have created a new Drupal TWG twitter account to announce the list of issues for consideration, this list will be posted on the Core groups.drupal.org group and linked from the twitter account.

All coding standards issues have been moved from the Technical Working Group issue queue to the new Coding Standards project, the maintainers of which will be the Coding Standards Committee. The Committee will be composed of members appointed by the Technical Working Group and any documentation maintainers (listed in Drupal Core’s maintainers.txt) will be automatically invited to join.

Meetings are held every two weeks where new issues can be identified for inclusion. The first meeting to review and include issues for the first round of updates to coding standards has been scheduled for January 22nd, at which time the committee will review coding standards issues tagged “Needs announcement for final discussion". Issues that are deemed ready by the committee will be included in the announcement following that meeting, at which time a final round of community feedback on the proposed changes will be appreciated. At a subsequent meeting the final discussion will be evaluated and issues may be ratified as official changes.

Categories: Planet Drupal

Drupal 8 core release on Wednesday, January 6

January 5, 2016 at 3:17am
Start:  2016-01-06 00:00 - 23:30 UTC Organizers:  catch xjm Event type:  Online meeting (eg. IRC meeting)

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.

To ensure a reliable release window for the patch release, there will be a Drupal 8.0.x commit freeze from 00:00 to 23:30 UTC on January 6. This is a good time to update your development/staging servers to the latest 8.0.x-dev code and help us catch any regressions in advance. If you do find any regressions, please report them in the issue queue. Thanks!

To see all of the changes since 8.0.1 that will be included in the release, see the 8.0.x commit log.

Other upcoming core release windows after this week include:

  • Wednesday, January 20 (security release window)
  • Wednesday, February 3 (patch release window)

For more information on Drupal core release windows, see the documentation on release timing and security releases, as well as the Drupal core release cycle overview.

Categories: Planet Drupal

Announcing Drupal 8 Contrib Office Hours

January 4, 2016 at 5:47pm

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:

Hope to see you there! :D

Categories: Planet Drupal

Drupal core security release window on Wednesday, December 16, 2015

December 11, 2015 at 7:00pm
Start:  2015-12-16 (All day) UTC Organizers:  xjm catch David_Rothstein Event type:  Online meeting (eg. IRC meeting)

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).

There will be no bug fix or feature release on this date. The next window for a Drupal core patch (bug fix) release for all branches is Wednesday, January 6, 2016. The next scheduled minor (feature) release for Drupal 8 will be on April 20, 2016.

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.

Categories: Planet Drupal

What's next for core patches after 8.0.0?

November 25, 2015 at 1:03am

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.

Now that Drupal 8 is ready for building real sites, with contributed projects already available or being built, the immediate focus for Drupal 8 core will be fixing bugs to help those real sites, as well as fixing any issues in Drupal core that prevent contributed modules from being ported to Drupal 8. Another top priority is stabilizing and completing the core Migrate feature and its user interface, so that existing Drupal 7 and especially Drupal 6 sites can move to Drupal 8 reliably. Finally, a third priority is adding frontend and performance testing to help us make changes more safely. For the next six weeks, we will mainly be committing patches that move us toward these three goals.

Then, after January 6, 2016, we will begin a broader feature development phase for innovations in 8.1.x, 8.2.x, and beyond, so long as we are able to resolve critical issues consistently and keep 8.1.x stable for a reliable scheduled minor release. Read more about the proposed development, beta, and release candidate phases for minor versions.

Drupal 8 core branches and the core issue workflow

Starting today, all patches that are accepted to core according to the priorities above will be committed first to the 8.1.x git branch (even when they are filed against 8.0.x-dev in the core issue queue). Patches that are eligible for patch releases will typically be immediately committed to 8.0.x as well. If we are close to a bugfix release window, the issue may be marked "Patch (to be ported)" and committed just after the bugfix release, to give ample time to catch any regressions or followups before each change is deployed to production sites.

Some patches will only be committed to 8.1.x (for example, if they are too disruptive for a patch release or if they make additions that are only allowed in minor releases). Keep in mind that the open feature development phase for 8.1.x has not started yet, so plan to work on general feature additions and BC-compatible API improvements after it does.

Note that for the time being, patch-release-eligible issues are still filed against 8.0.x-dev in the core issue queue and most 8.1.x issues are still postponed pending the open feature development phase. Later, we will update the core issue metadata and processes as we move into more extensive minor version development.

Categories: Planet Drupal

Drupal core security release window on Wednesday, November 18

November 13, 2015 at 9:24pm
Start:  2015-11-18 (All day) America/New_York Organizers:  David_Rothstein Event type:  Online meeting (eg. IRC meeting)

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).

There will be no bug fix/feature release on this date; the next window for a Drupal core bug fix/feature release is Wednesday, December 2 (and before that, on November 19, Drupal 8.0.0 is scheduled to be released).

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.

Categories: Planet Drupal

CHANGELOG.txt is being updated to prepare for D8 release. What changes to you want highlighted?

November 13, 2015 at 7:52pm

CHANGELOG.txt is being updated to prepare for D8 release. What changes to you want highlighted?

See issue: https://www.drupal.org/node/2606334

Categories: Planet Drupal

Proposal: D8 Core Office Hours

November 9, 2015 at 9:25pm

(Stretching the definition of "core" 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.

After talking to numerous project maintainers, including those with multiple Drupal 8 core commits, it seems like many would find value in having dedicated times during which to collaborate with other people porting projects to D8, get questions answered, get advice on sticky problems, and figure out where best to help.

If you'd like to help mentor these sorts of office hours, please add your name to the issue summary at http://www.drupal.org/node/2612094 and fill in the Doodle.

Rock!

Categories: Planet Drupal

Drupal 8.0.0-rc4 on Thursday, November 12, 2015

November 6, 2015 at 9:22pm
Start:  2015-11-12 16:00 - 17:00 America/Chicago Organizers:  xjm catch Event type:  Online meeting (eg. IRC meeting)

In preparation for the scheduled release of Drupal 8.0.0 on Thursday, November 19, we will create the final release candidate for Drupal 8.0.x, Drupal 8.0.0-rc4, on Thursday, November 12. We have added this release candidate in addition to the scheduled release windows to provide a final testing target for changes during the RC phase. (Unlike other release candidates, this release window will not include a 24-hour code freeze.) Plan to help test this final release candidate for bugs and regressions during the final week before 8.0.0's release!

Following RC4, we will further restrict the patches we commit to severe bugs or regressions and documentation fixes only, at committer discretion. So, if you have any allowed RC changes underway, plan to complete them by November 12.

There will not be a separate release candidate on November 18. (The November 19 release date is an extension of the November 18 release window.)

Categories: Planet Drupal

No Drupal 6 or Drupal 7 core release on Wednesday, November 4

November 2, 2015 at 6:04pm

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)

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.

Categories: Planet Drupal

Pages