Subscribe to Drupal core announcements feed
Core announcement
Updated: 2 hours 48 min ago

Drupal core security release window on Wednesday, May 20

May 18, 2015 at 5:02am
Start:  2015-05-20 (All day) America/New_York Online meeting (eg. IRC meeting) Organizers:  David_Rothstein

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

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, June 3.

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

Drupal 8 beta 11 on Wednesday, May 27, 2015

May 12, 2015 at 10:56pm

The next beta release for Drupal 8 will be beta 11! (Read more about beta releases.) The beta is scheduled for Wednesday, May 27, 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 May 27.

Categories: Planet Drupal

Drupal 8 Question-and-Answer Core Conversation at DrupalCon Los Angeles

May 6, 2015 at 11:05pm

Do you have questions about the upcoming Drupal 8 release (or Drupal 8.1.x or 9 and beyond)? On Thursday, May 14 at DrupalCon Los Angeles, I'll be moderating a question-and-answer core conversation with a panel of the Drupal 8 core committers. Questions can be submitted in advance online, and anyone can submit a question (or more than one). I will curate the submissions to ask the panel the most interesting and relevant questions.

Some suggested topics:

  • Drupal core's newly refined structure and decision-making process (see my earlier post for background information).
  • Contributing as a core subsystem or topic maintainer
  • The upcoming Drupal 8.0.0 release: what to expect and how we're going to get there
  • Any questions you have for core committers
  • Or anything else on your mind!

This is a rare opportunity for the community to communicate directly with the Drupal 8 committer team. Help us make the most of of it -- submit your questions now!

Categories: Planet Drupal

Drupal core updates for May 6th, 2015

May 6, 2015 at 6:42pm

Congratulations to Alex "effulgentsia" Bronstein and Jess "xjm", who became core committers as part of the Evolving and documenting Drupal core's structure, responsibilities, and decision-making policy (which could still use your review)!

What's new with Drupal 8?

Since the last Drupal Core Update, the minimum version of MySQL needed to run D8 was raised to 5.5.3, and Drupal 8.0.0-beta10 was released in time for DrupalCon Los Angeles (which is next week).

Some other highlights of the month were:

How can I help get Drupal 8 done?

See Help get Drupal 8 released! for updated information on the current state of the release and more information on how you can help.

We're also looking for more contributors to help compile these posts. Contact mparker17 if you'd like to help!

Drupal 8 In Real Life Whew! That's a wrap!

Do you follow Drupal Planet with devotion, or keep a close eye on the Drupal event calendar, or git pull origin 8.0.x every morning without fail before your coffee? We're looking for more contributors to help compile these posts. You could either take a few hours once every six weeks or so to put together a whole post, or help with one section more regularly. If you'd like to volunteer for helping to draft these posts, please follow the steps here!

Categories: Planet Drupal

Drupal 7 core release on Wednesday, May 6

May 5, 2015 at 5:39am
Start:  2015-05-06 (All day) America/New_York Online meeting (eg. IRC meeting) Organizers:  David_Rothstein

The monthly Drupal core bug fix/feature release window is this Wednesday, May 6. Although there was a release just last month, it's a good time for another one, to fix a regression introduced in Drupal 7.36 that affected some sites as well as to get a few other fixes in. Therefore, I plan to release Drupal 7.37 this Wednesday.

The final patches for 7.37 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.

The primary purpose of this release is to fix a regression caused by Drupal 7.36 which caused content types on some existing sites to become disabled after the update (see the 7.36 release notes and the issue for further information). The fix is intended to work for sites that already upgraded to Drupal 7.36 (it should restore content types that were erroneously disabled) as well as for those that did not. More testing of this issue in particular is welcome.

You might also be interested in the tentative CHANGELOG.txt for Drupal 7.37 and the corresponding list of important issues that will be highlighted in the Drupal 7.37 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 20 (security release window)
  • Wednesday, June 3 (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

Drupal core updates for April 22nd, 2015

April 22, 2015 at 4:28pm
What's new with Drupal 8?

Happy Earth Day! Since the last Drupal Core Update, the Drupal Developer Days event brought lots of exciting progress: we (briefly) reduced the number of critical issues to 35, and a week-long performance sprint made Drupal 8 2—20 times faster! Also, Gwendolyn Anello at DrupalEasy announced that DrupalEasy is partnering with Stetson University to offer Drupal courses!

Some other highlights of the month were:

How can I help get Drupal 8 done?

See Help get Drupal 8 released! for updated information on the current state of the release and more information on how you can help.

We're also looking for more contributors to help compile these posts. Contact mparker17 if you'd like to help!

Drupal 8 In Real Life Whew! That's a wrap!

Do you follow Drupal Planet with devotion, or keep a close eye on the Drupal event calendar, or git pull origin 8.0.x every morning without fail before your coffee? We're looking for more contributors to help compile these posts. You could either take a few hours once every six weeks or so to put together a whole post, or help with one section more regularly. If you'd like to volunteer for helping to draft these posts, please follow the steps here!

Categories: Planet Drupal

Drupal 8 beta 10 on Wednesday, April 29, 2015

April 22, 2015 at 8:18am

The next beta release for Drupal 8 will be beta 10! (Read more about beta releases.) The beta is scheduled for Wednesday, April 29, 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 April 29.

Categories: Planet Drupal

Drupal core security release window on Wednesday, April 15

April 13, 2015 at 2:51pm
Start:  2015-04-15 (All day) America/New_York Online meeting (eg. IRC meeting) Organizers:  David_Rothstein

The monthly security release window for Drupal 6 and Drupal 7 core will take place on Wednesday, April 15.

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, May 6.

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

D8 Accelerate Performance Sprint at Drupal Developer Days in Montpelier, France

April 2, 2015 at 9:54pm
Start:  2015-04-13 (All day) - 2015-04-19 (All day) Europe/Paris Sprint Organizers:  Wim Leers

http://montpellier2015.drupaldays.org

The goal of this sprint is to uncover the "unknown unknowns" blocking Drupal 8 from shipping, performance-wise. The main focus will be on profiling Drupal 8 under a variety of scenarios to determine the next places to start optimizing, then creating issues for these things so that a wider group of folks can work on them.

We're specifically looking for two types of sprinters:

  1. Finders: Those with profiling experience, using tools like XHProf, Blackfire, and flame graphs, who can analyze profiling data to flag problems and come up with recommendations on optimization targets. Your goal is to keep drilling down until we get to the bottom of what's making Drupal 8 slow.
  2. Fixers: Those who can both work on existing known performance issues, as well as take direction from the first group and create/review patches to improve areas of performance. We're especially looking for those with experience with things like the routing system, bootstrapping, container services, route access checking, and asset handling.

The Sprint Planning Doc has everything you need to know, including stuff to do before the sprint and a nice list of all the outstanding critical issues to tackle.

If you're planning to attend (remote attendees welcome!) fill your details in the DevDays Sprint Attendance sheet.

Hope to see you there!

Categories: Planet Drupal

Drupal core updates for April 2nd, 2015

April 2, 2015 at 8:15pm

Welcome to the second quarter of 2015! In the past two weeks, Dries proposed an evolution to Drupal core's structure and decision-making process, the Drupal Community mourned the passing of Aaron Winborn and the Drupal Association announced The Aaron Winborn Award to honor amazing community members in his memory, Addison Berry was elected the 2015 Drupal Association Director At-Large, and lastly, a group to help mentors was formed.

What's new with Drupal 8?

Since the last Drupal Core Update, Drupal 8.0.0-beta9 was released (beta8 was skipped due to installer issues), all known critical issues with the Drupal 8 configuration system were fixed, and the taxonomy term reference field was removed in favor of entity reference fields.

Some other highlights of the month were:

How can I help get Drupal 8 done?

See Help get Drupal 8 released! for updated information on the current state of the release and more information on how you can help.

You can also raise money and/or donate to the Drupal 8 Accelerate grant program to fund Drupal 8 contribution sprints. For more information about how your donations are used, see webchick's detailed analysis.

We're also looking for more contributors to help compile these posts. Contact mparker17 if you'd like to help!

Drupal 8 In Real Life Whew! That's a wrap!

Do you follow Drupal Planet with devotion, or keep a close eye on the Drupal event calendar, or git pull origin 8.0.x every morning without fail before your coffee? We're looking for more contributors to help compile these posts. You could either take a few hours once every six weeks or so to put together a whole post, or help with one section more regularly. If you'd like to volunteer for helping to draft these posts, please follow the steps here!

Categories: Planet Drupal

Drupal 7 core release on Wednesday, April 1

March 31, 2015 at 6:32am
Start:  2015-04-01 (All day) America/New_York Online meeting (eg. IRC meeting) Organizers:  David_Rothstein

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:

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.

Categories: Planet Drupal

Plan for upcoming D8 Accelerate sprint on DrupalCI (Modernizing Testbot Initiative)

March 25, 2015 at 9:54pm

Next week, an international conglomeration of awesome folks will convene in Portland, Oregon for a D8 Accelerate-funded sprint on DrupalCI: Modernizing Testbot Initiative.

The main aim of DrupalCI is to rebuild Drupal's current testbot infrastructure (which is currently powered by an aging Drupal 6 site) to industry-standard components such as Jenkins, Docker, and so on, architected to be generally useful outside of Drupal.org. See Nick Schuch's Architecting DrupalCI at DrupalCon Amsterdam blog post for more details.

The goal is to end the sprint with an "MVP" product on production hardware, with integration to Drupal.org, which can be used to demonstrate a full end-to-end D8 core ‘simpletest’ test run request from Drupal.org through to results appearing on the results server.

You can read and subscribe to the sprint hit-list issue to get an idea of who's going to be working on what, and the places where you too can jump in (see the much longer version for more details).

This is a particularly important initiative to help with, since it not only unblocks Drupal 8 from shipping, it also makes available awesome new testing tools for all Drupal.org projects!

Go Team! :)

Categories: Planet Drupal

Drupal 8 beta 8 TOMORROW on Wednesday, March 25, 2015

March 24, 2015 at 4:24pm

The next beta for Drupal 8 will be beta 8! Here is the schedule for the beta release.

Wednesday, March 25, 2015 Drupal 8.0.0-beta8 released. Emergency commits only.
Categories: Planet Drupal

This Month In Drupal Documentation (March 2015)

March 24, 2015 at 3:27am

Here's an update from the Documentation Working Group (DocWG) on what has been happening in Drupal Documentation in the last month or so. Sorry... because this is posted in the Core group as well as Documentation, comments are disabled.

If you have comments or suggestions, please see the DocWG home page for how to contact us. Thanks!

Notable Documentation Projects and Updates

Progress is being made on [meta] Update or create hook_help() texts for D8 core modules, there are only a few child issues left before we can close that issue, and all celebrate the updated help text being ready for Drupal 8.

In addition we would love to see people putting some energy into reviewing existing help text for each of the core modules, and filing issues for anything that needs to get fixed. See [META] Review hook_help texts & copy text to drupal.org, which has some really great step-by-step instructions for doing a review. These reviews are something that you can generaly do in 30 minutes or less, and don't even require setting anything up on our localhost. So jump on in and lets knock these out.

Thanks for contributing!

Since March 1st, 2015 – 189 contributors have made 554 total Drupal.org documentation page revisions, including 9 people that made more than 10 edits -- thanks everyone! And, there are still a few days left in the month.

  • Pierre.Vriens (54 revisions)
  • gisle (25 revisions)
  • Spleshka (25 revisions)
  • Wim Leers (20 revisions)
  • nedjo (17 revisions)
  • NonProfit (17 revisions)
  • valderama (12 revisions)
  • lolandese (11 revisions)
  • sidharrell (11 revisions)

In addition, there were many many commits to Drupal Core and contributed projects that improved documentation -- these are hard to count, because many commits combine code and documentation -- but they are greatly appreciated too!

Documentation Priorities

The Current documentation priorities page is always a good place to look to figure out what to work on, and has been updated recently.

If you're new to contributing to documentation, these projects may seem a bit overwhelming -- so why not try out a New contributor task to get started?

Upcoming Events

Want to help out with documentation? Do so in person at one of these upcoming events:

Report from the Working Group

Over the last couple of months we've been hard at work going over proposals for updates to Drupal.org put forth by the Drupal Association and other working groups. Each of the Drupal.org working groups has purview over different areas of keeping Drupal.org up and running, and figuring out how to make it even better in the future. As you can imagine, with the huge amount of documentation on Drupal.org there's a fair amount of things that touch on elements that the DocsWG helps to oversee. In our last couple of meetings we've had the opportunity to meet with members of the DA, and to talk about their 2015 priorities and roadmap. In doing so we've gotten some insight into how that will compare with the things we had outlined as priorities with regards to documentation. And begun to explore ways in which we can continue to collaborate in the future to make the process of writing, reading, and maintaining documentation on Drupal.org even better.

While it hasn't all been fun and games, both sides are working to ensure that we have better processes for communicating going forward.

This gist of it at this point is that while not everything on our list is part of their roadmap – there is a fair amount of overlap and we're looking forward to seeing how it all plays out over the coming months. That said, if you've ever felt like contributing to Drupal.org yourself there are some great opportunities to get involved with helping to improve our infrastructure. And both the DocsWG and the DA would always love the help. Reach out to any of us if you have questions.

Until next time. Happy documenting!

Categories: Planet Drupal

Evolving and documenting Drupal core's structure, responsibilities, and decision-making

March 23, 2015 at 4:41pm

The Drupal project just turned 14 years old. There are now over 1 million known installations of Drupal, and Drupal.org has over 1 million users. Drupal 8 has over 2,700 contributors (almost three times that of Drupal 7) and over 13,000 commits so far (50% more commits per day on average than Drupal 7). I wanted to take an opportunity to reflect on our current governance structure and try to evolve the Drupal leadership team and decision-making, enable better scaling, and document both the formal and informal processes we have currently in place.

Over in the Drupal core issue queue, I've proposed an evolution to Drupal core's structure and decision-making process which documents how things are currently done, and also proposes some incremental improvements:

  1. Defines roles and responsibilities that are currently carried out by individuals within the core committer team: product managers, framework managers, and release managers. This is done to provide transparency, to help expedite decision-making, and to ensure that these roles are easier to fill in the future, as we can eliminate the requirement for core committers to be “superhuman” contributors capable of doing anything and everything, at all times.
    • This document also adds the concept of “provisional” product, framework, and release managers, without actual commit access, who work alongside the core committers until they gain the necessary experience to play a full committer role.
    • In so doing, the document also appoints two additional core committers—Alex Bronstein (effulgentsia) and Jess (xjm)—who have been playing this "provisional" role for some time now, informally.
  2. Lays out an explicit decision-making framework to make it clear who needs to be involved in what types of changes, and to what degree. This documents the process we already use, but also introduces some changes. The added transparency should make it easier for contributors who are proposing changes to direct their questions to the right people.
  3. Clearly outlines the role of subsystem maintainer (formerly component maintainer) as an active “maintenance” role: performing or organizing regular maintenance tasks: triaging the subsystem's queue(s), reviewing patches in need of review, etc. These responsibilities also come with a more formal opportunity to sign off on proposed changes that significantly affect the subsystem. The advantages to this are additional transparency, delegating and scaling responsibilities, and reducing the workload that currently falls to core committers. Going forward, subsystem maintainers who are not currently active will no longer be listed in MAINTAINERS.txt.

This document builds on ideas that have been blogged about or presented at Drupal events by many people, including Randy Fay (rfay), Larry Garfield (Crell), Cathy Theys (YesCT), Gábor Hojsty, Greg Dunlap (heyrocker), Jess (xjm), Alex Pott (alexpott), Nat Catchpole (catch), Jennifer Hodgdon (jhodgdon) and others. It has been reviewed by numerous people, including the existing core committer team. Special thanks to Angie Byron who has spent weeks helping me co-author this proposal.

Categories: Planet Drupal

Plan to finalize the Migration system

March 23, 2015 at 4:56am

If you move to Drupal 8 from Drupal 6/7, you'll be using the new core migration system.

Migrate team lead benjy has just posted a plan to finalize the migration system, a "meta" issue which outlines what work's already been completed, what's left to be done, what's blocking what, and how to get involved.

Migrations are an extremely high-impact place to throw time and energy, so if fixing Drupal 8 release blockers isn't your thing, but being able to actually move to Drupal 8 when it's ready is, please jump in and lend a hand! :D (Especially if you've worked with Migrate module in D7 contrib.)

Categories: Planet Drupal

Propsed policy: Re-activate the head2head project and use it for D8 beta-to-beta upgrades in the short-term

March 19, 2015 at 9:37pm

In order to support a beta-to-beta upgrade path for Drupal 8 users sooner, the core committers have posted a proposal that recommends re-activating the http://drupal.org/project/head2head project in contrib and building the beta-to-beta upgrade path there in the short-term. This allows early adopters to have access to an upgrade path much earlier than core would be able to provide, and also gives us a "safe space" to test beta-to-beta upgrades prior to supporting them formally in core, without slowing down our current velocity on critical issue fixing.

Please share your thoughts, especially if you're one of the adventurous early adopters who are actively building on Drupal 8 already!

Categories: Planet Drupal

Drupal core updates for March 18th, 2015

March 18, 2015 at 3:12pm
What's new with Drupal 8?

Since the last Drupal Core Update, the Drupal community has reduced the number of D8 critical issues to 45, and managed to keep the number of critical issues on one pagesince we hit 50 criticals on March 6th! We've also changed the behavior of the "admin role" setting so that any user with the "admin role" passes all permission checks automatically (like the superuser); added HTML5-lib to core so that HTML5 can be parsed properly; and fixed a bug preventing all PHPUnit tests from running.

Also, after a few months of work, the Technical Working Group, Drupal.org Software Working Group, Security Working Group, and frequent project application reviewers presented their proposed changes to the project application review process. They're looking for your feedback, so please read their proposal and leave your thoughts!

Some other highlights of the month were:

How can I help get Drupal 8 done?

See Help get Drupal 8 released! for updated information on the current state of the release and more information on how you can help.

We're also looking for more contributors to help compile these posts. Contact mparker17 if you'd like to help!

Drupal 8 In Real Life

Voting in the Drupal Association's 2015 At-Large Board Elections ends Friday, so this is your last chance to make your voice heard! Anyone with a Drupal.org account that was created before the time nominations opened (January 31, 2015), and who has logged in at least once in the past year is allowed to vote, even if they are not a member of the Drupal Association!

Some other events happening in the coming weeks are:

Whew! That's a wrap!

Do you follow Drupal Planet with devotion, or keep a close eye on the Drupal event calendar, or git pull origin 8.0.x every morning without fail before your coffee? We're looking for more contributors to help compile these posts. You could either take a few hours once every six weeks or so to put together a whole post, or help with one section more regularly. If you'd like to volunteer for helping to draft these posts, please follow the steps here!

Categories: Planet Drupal

Drupal core security release window on Wednesday, March 18

March 16, 2015 at 4:12am
Start:  2015-03-18 (All day) America/New_York Online meeting (eg. IRC meeting) Organizers:  David_Rothstein

The monthly security release window for Drupal 6 and Drupal 7 core will take place on Wednesday, March 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, April 1.

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

This month in Drupal documentation (February 2015)

March 9, 2015 at 9:09pm

Here's an update from the Documentation Working Group (DocWG) on what has been happening in Drupal Documentation in the last month or so. Because this is posted in the Core group as well as Documentation you can not comment on this post. If you have comments or suggestions, please see the DocWG home page for how to contact us.

Notable Documentation Updates

Most of the hook_help texts for the Drupal 8 core modules have been finished, but there are still a few that some review. If you can help, hop over to https://www.drupal.org/node/1908570 to find the remaining issues. Most of these help texts need to a review because they have been written over a course of two years and Drupal 8 has evolved since then. If you want to help reviewing them, check https://www.drupal.org/node/2283477.

Thanks for doocumenting

February 2015 was a extraordinary productive documentation month with 245 people revising and writing more than 1000 pages. The most active editors were:

Many thanks go out to everyone that helped improving Drupal's on line documentation.

Documentation Priorities

The Current documentation priorities page is always a good place to look to figure out what to work on, and has been updated recently.

The two meta issues to update and review of help texts currently have a high priority: Not only do we need them for a good user experience of Drupal 8, they also need to be translated once they are ready.
Working on them is also a good way to find out already how Drupal 8 will work for site builders and site administrators.

If you're new to contributing to documentation, these projects may seem a bit overwhelming -- so why not try out a New contributor task to get started?

Upcoming Events

Report from the Working Group

In February, we met with the Drupal Association's Joshua and Tatiana who presented us the ideas for the future of on line documentation on drupal.org. It seems that in the future we will be able to use several different types of documentation on drupal.org, most noticeably we will be able to have documentation that is much tighter integrated with contributed modules and themes. We were able to give useful feedback on the DA's plans and some of our long wished improvements, as outlined in https://www.drupal.org/governance/docwg-goals seem to be going to be realised. Despite that, some of our requests have not been met yet and some doubts remain over the implementation of the DA's plans.

Categories: Planet Drupal

Pages