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

Approachable tasks for Drupal 8 Beta 1

April 21, 2014 at 1:28am

If you couldn't make the (nearly) back-to-back sprints on beta-blocking issues at Drupal DevDays Szeged and NYC Camp, don't worry! We still have some leftover sprint tasks that will help with the first Drupal 8 beta release. Many of the 27 remaining beta blockers require deep knowledge of the problem space; however, the tasks listed here (while not necessarily quick or easy) are more approachable and self-contained. Some of these issues are beta-blocking in their own right; others are "beta target" issues that would ideally be done for a beta release even if they aren't critical enough to block it.

If you're new to core contribution or Drupal 8, check out the Core Contribution Mentoring program instead.

Sprinters at the beta sprint, wearing bunny ears.

Documenting Critical Drupal 8 APIs

#1988612: Change record: Apply formatters and widgets to rendered entity base fields

Entities in Drupal 7 and 8 have two kinds of field data: base fields (or properties in Drupal 7), like the node author field or the taxonomy term description, and configurable field instances, which can be attached to a given fieldable entity type's bundles through the user interface. Previously, it was not possible to use widgets or formatters for base fields, so they typically use custom form elements and rendering code that are not compatible with Drupal 8's in-place editing functionality. Since December, however, it is possible to use widgets and formatters on base fields -- but there is no change record yet for this improvement.

#2244777: Document in WSCCI change notice or handbook all the menu changes (tasks, actions, contextual links, menu links) from 7 to 8

In order for contrib developers to make good use of our first beta release, we need good documentation of the new Drupal 8 routing and menu systems. The first step is to thoroughly document exactly how a Drupal 7 module's hook_menu() is upgraded to Drupal 8, and the exisitng change record is only partially complete. Join the discussion on this issue and help us complete this critical documentation.

#2046367: Document the internals of the router

While not explicitly beta-blocking at this point, more complete API documentation for the routing system overall will be very valuable to contributed module developers using the first beta release. Help improve the routing documentation both in the Drupal.org handbook and in the Druapl 8 codebase.

#2235363: Document how plugin definitions should declare config dependencies

This is a documentation followup for one small API change that supports the new configuration dependency system. It sits at the intersection of two new (and complicated) Drupal 8 APIs: plugin derivatives and the configuration entity system. Most of the confusing work for this issue is done, and it has resulted in a new handbook page on configuration entity dependencies. The remaining task is to add documentation of the config_dependencies key in plugin derivative definitions to the API documentation in the codebase. (See under "Calculating dependencies in plugins and their derivatives" on the handbook page.) The handbook page, which is about configuration dependencies generally, also needs further work, but that is not blocking for this issue.

Configuration system

#2224761: Translation sync should be stored in own storage instead of injected in field instance settings

This issue for the content translation module changes the way some of the module's configuration is stored. It's an easier change to implement compared to other deep architectural beta blockers for the Configuration system and the Entity Field API, but it still needs some work to resolve. The next step is to incorporate the latest feedback in comments #24 through #27 on the issue. This is also a great spot for multilingual initiative contributors to help with the beta.

#2140511: Configuration file name collisions silently ignored for default configuration

This critical configuration system bug isn't a hard blocker for the beta release, but it can cause significant problems. An in-progress patch on the issue needs test failures resolved, updates for the latest changes in the configuration system, and other improvements.

Entity Field API

#2016679: [Meta] Expand Entity Type interfaces to provide methods

Drupal 8 core provides numerous entity types, but the full API for each type is not easily documented or discoverable, since the entity's properties are accessed through magic getters. To improve the developer experience, each entity type interface is being expanded with relevant methods for the specific entity. (For example, NodeInterface now has methods like isPromoted(), isPublished(), getTitle(), and setTitle().) All the methods for content entity types have been added, but only 1/4 of the configuration entity type interfaces are complete. Most issues have a submitted patch, and what is most needed is architectural review of the proposed interface methods. (For example, see comment #19 on the FieldConfig issue.) If you have experience with one of the subsystems that still has an open child issue, or if you have a sound grasp on OO design generally, we could use your help to thoroughly review these patches so that the completed APIs are available for contributed module developers in a beta release.

#2190313: Add $EntityType::load() and loadMultiple() to simplify loading entities

In a similar vein of improving the entity system's developer experience by making the API more discoverable and removing exposure to internal concepts, this issue adds static methods for loading the entities of each type. The patch needs to be rerolled to apply to HEAD, and then needs architectural review.

#2010930: [META] Apply formatters and widgets to rendered entity base fields

Remember that issue above about widgets and formatters for base fields? We also need to convert base fields other than the node title to also use widgets and formatters rather than custom code. This isn't considered beta-blocking, but it will change how contributed module developers interact with these entity types (plus make it so that in-place editing behaves in a more expected fashion). The several child issues of this meta (one per entity type) need either further work on the patch or code review. If you're somewhat familiar with entities and fields in Drupal 8, this is a good place to help.

Views conversions

#1823450: [Meta] Convert core listings to Views

One of the major benefits of having Views in core is that legacy one-off listings in core can be replaced with user-configurable views. Views is used in numerous places in core already, for example, the user and content administration screens, the promoted node frontpage and RSS feed, and numerous blocks like the "Recent content" and "Who's online" blocks. A handful of more complicated legacy core listings still need to be converted to views. These conversions don't block a beta release, but are targeted for the beta since adding them involves removing legacy API functions. In particular, it would be valuable to complete the conversions of the comment admin page and the taxonomy term pages to views for a beta release. Additionally, replacing the content revision table with a view is blocked on a major views bug related to content revisions.

Categories: Planet Drupal

Migrate in core weekly calls resume

April 16, 2014 at 4:22pm
Start:  2014-04-17 15:00 - 15:30 America/Vancouver Online meeting (eg. IRC meeting) Event url: 

https://plus.google.com/106269343178096590461/

After a month hiatus, at a new timeslot we resume our weekly Migrate in core Google Hangouts, focusing on Drupal 7.

The time is 3PM in Vancouver, 6PM in Boston, midnight in Europe (sorry) and 6AM in Perth -- coordinating across this many timezones was very hard and Europe got the short stick. Sorry.

Categories: Planet Drupal

Drupal core security release window on Wednesday, April 16

April 14, 2014 at 5:18am
Start:  2014-04-16 (All day) America/New_York Sprint Organizers:  David_Rothstein

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

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 release on this date; the next window for a Drupal core bug fix release is Wednesday, May 7.

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

Help unblock Drupal 8.0-beta1 at the NYC Camp Drupal 8 sprint

April 9, 2014 at 4:42pm
Start:  2014-04-10 (All day) - 2014-04-12 (All day) America/New_York Sprint Organizers:  xjm Event url: 

http://www.nyccamp.org/event/d8-core-sprint

After three years of Drupal 8 development, we are finally closing in on a Drupal 8.0-beta1 release. Of about 150 critical issues that have blocked the first Drupal 8 beta release, only 32 beta blockers remain. Most of these remaining issues are too complex for any one developer to resolve alone, but we need help on numerous tasks that will accelerate them. Join us at the NYC Camp D8 Core Sprint to see firsthand the work that's in progress and contribute to our momentum. Look for the "IRL issue queue" on colored construction paper at the sprint. :)

(New to Drupal 8 or core contribution? Check out the Get Involved with Core sprint instead.)

Categories: Planet Drupal

This week-ish in Drupal core: April 2, 2014

April 2, 2014 at 9:32pm
What's new with Drupal 8?

The past three weeks saw some exciting progress on Drupal 8, in part due to the hard work of everyone who went to DrupalDevDays 2014 in Szeged, Hungary. It also saw the release of drupal-8.x-alpha10.

Drupal Developer Days Szeged

DevDays Szeged was a landmark for the Drupal 8 release cycle. Participants marveled at how productive and well-organized the event was, and core maintainers commented they'd never seen such momentum in the RTBC queue. During the week-long sprint, 19 beta blocking issues were fixed (with three more RTBC) and every single missing change record was written. Outside core, sprinters also made significant progress on everything from the Search API module for Drupal 8 to Drupal.org itself. A robot doll, chocolates, bunny ears, stickers, and Drupal-ified Hungarian folk music also made it the event of the year. (Szeged slide show)

Sprinters at DevDays Szeged wearing bunny ears, in front of colored issue charts.

Alpha 10 released; Alpha 11 due Apr. 23

Alpha 10 was released on March 19th, just before Drupal Dev Days. Some notable changes include:

... for the full list of changes, see the alpha 10 release notes.

These alphas are provided to give you something more stable to work off of than having to chase HEAD every day.

Where's Drupal 8 at in terms of release?

Core momentum increased again in March, with a new all-time record of 51 criticals fixed over the month. In fact, we've nearly recovered to the level of known technical debt we had as of feature freeze a year ago. :P There's still a long ways to go, so help us focus on the most important issues and on releasing a sound Drupal 8 beta.

A graph of the outstanding critical issues per month since 2011, showing a steep decline this month.

Our steady progress toward that first beta release continues as we divide the outstanding beta blockers into actionable sub-steps. Among March's fixed criticals were over 30 beta blockers, more than half the total, showing the community's tight focus on unblocking this milestone.

Graph indicating the numbers of beta blocker, beta target, and change record issues outstanding since Jan. 1 2014.
Note that the number of beta target issues (which are issues that would be good to resolve for the beta, but are not critical enough to block it) continues to increase. As we get closer to beta, it's important to also pay attention to these issues, so we'll be highlighting beta targets more in the coming weeks.

Last week, we fixed 25 critical issues and 24 major issues, and opened 15 criticals and 29 majors. That puts us overall at 118 release-blocking critical issues and 486 major issues.

16 beta-blocking issues were fixed last week. There are still 28 of 142 beta blockers that must be resolved before we can release a Drupal 8 beta.

Where can I help?

Top criticals to hit this week

Each week, we check with core maintainers and contributors for the "extra critical" criticals that are blocking other work. These issues are often tough problems with a long history. If you're familiar with the problem space of one of these issues and have the time to dig in, help drive it forward by reviewing, improving, and testing its patch, and by making sure the issue's summary is up to date and any API changes are documented with a draft change record.

More ways to help

Love Drupal and want to help out, but not a coder or unsure where to start? From breaking things (for science!), to designing things; from summarizing issues to writing documentation, there's lots of ways you can contribute! And, there are more than 125 mentors willing to help you!

Our current priority is updating the documentation for Drupal 8. Rich, helpful documentation for Drupal 8 is incredibly important: it's a great way to market Drupal to potential clients, it saves you from writing as much documentation for your existing clients, it empowers new users, site builders, developers, and themers to learn and solve their problems; and, with all the changes that have happened since Drupal 7, it's pretty useful for seasoned Drupal veterans as well!

The documentation team is working on updating:

... for more information, visit the #drupal-docs channel on IRC or jump into the documentation issue queue.

As always, if you're new to contributing to core, check out Core contribution mentoring hours. Twice per week, you can log into IRC and helpful Drupal core mentors will get you set up with answers to any of your questions, plus provide some useful issues to work on.

Notable Commits

The best of git log --after=2014-03-12 --pretty=oneline (253 commits in total):

Amazing work on the configuration system's architecture and dependency management, notably:

  • Issue #2080823 by alexpott, swentel, Wim Leers: Create API to discover content or config entities' soft dependencies and use this to present a confirm form on module uninstall.
  • Issue #2030073 by alexpott: Config cannot be imported in order for dependencies.
    You can now declare dependencies for configuration entities, so you can ensure their dependencies are met before importing them.
  • Issue #2219499 by Berdir, alexpott, Gábor Hojtsy, vijaycs85, swentel: Generalize language config override responsibility.
    This patch simplifies the way that language-specific overrides work and significantly reduces the amount of code that needs to run on sites with only one language.

And, we resolved some of the menu/routing issues that had been causing headaches for developers:

  • Issue #2178725 by pwolanin, crowdcg, effulgentsia, Sutharsan: Make all core menu link machine names and the corresponding route names match.
  • Issue #2226903 by pwolanin, dawehner, tvn, martin107, jessebeach: Step 1: Move static menu links to yml files.
    Now, default menu links are declared the same way as local tasks and local actions. (The next step is to finalize the underlying architecture for this change.)
  • Issue #2207893 by dawehner, pwolanin, jessebeach, Boobaa: Convert menu tree building to a service.
    This removes a whole bunch of the code in menu.inc, makes the menu-building code unit-testable and decouples it from other subsystems. It also unblocks beta-blocking work on the Menu Link API.

In the "things that always annoyed you about Drupal" category,

  • Issue #318975 by sun, Bojhan, linclark: Remove confirmation page after installation.
    When the installer is finished, it drops you on the front page of your new site!
  • Issue #340723 by ParisLiakos, sun, Berdir, glennpratt, Cottser, swentel, tstoeckler, Xano, tim.plunkett, BassistJimmyJam: Make modules and installation profiles only require .info.yml files.
    That means no more empty .module and .profile files! DX FTW!
  • Issue #2122693 by jayeshanandani, YesCT, sun, alexpott, BMDan: Installer does not work on a completely empty settings.php.
    This had been possible in D7.

Other notable commits:

  • Issue #2188613 by Berdir, Xen, andypost: Rename EntityStorageController to EntityStorage.
    This 600K patch was added to make it easier to distinguish between Entity storage classes and Routing controllers.
  • Issue #2213451 by andypost, bdone, benjy, penyaskito, chx, claudiu.cristea, damiankloip, gregboggs, InternetDevels, jessehs, jhedstrom, marvil07, mikeryan, pcambra, Xano, YesCT: Update Migrate API in core.
    This huge update to the migrate API adds support for requirements/dependencies; adds migrations for passwords, URL aliases and config entities; improves entity, bundle and field support; adds lots of Drupal 6 migrations; allows you to set the MigrateSource and MigrateDestination using annotations; and improves documentation. Awesome work Migrate team!
  • Issue #1194136 by Berdir, damiankloip, Wim Leers: Re-organise core cache bins.
    This groups cached items by the type of data (e.g.: rendered HTML, data, entity), rather than the type of item (e.g.: node, block, etc.). This will make cache bins for frequently-requested items (like configuration) smaller with less-frequent updates, which makes it easier for query caches. And, it allows you to tune performance by choosing the most-efficient storage engine / storage location for the type of data (for example, putting the configuration cache table in RAM or on an SSD).
  • Issue #2211553 by andypost, Berdir: Allow usage of entity_reference field widget and formatter for base fields.
    Entity reference fields are being used in core, but there had been no way to use it's widget and formatter.

You can also always check the Change records for Drupal core for the full list of Drupal 8 API changes from Drupal 7.

Drupal 8 Around the Interwebs

Here are a few notable blog posts about Drupal 8 in the past few weeks:

Drupal 8 in "Real Life"

If you would like to get away from the computer, meet other Drupal users, learn about Drupal 8, and have fun at the same time, you can look forward to:

  • NYC Camp on April 10-13: you can get Twig training, there are 13 accepted Drupal 8 sessions, 10 sprints scheduled and there's even a Core summit!
  • DrupalCamp Frankfurt 2014 in Frankfurt, Germany on April 12 and 13; with 8 proposed Drupal 8 sessions on everything from Twig to the Configuration Management Initiative.
  • Drupal Camp Japan 2014 in Kyoto on April 12, featuring an introduction to Drupal 8.
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.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 alpha 11 on Apr. 23

March 31, 2014 at 7:19pm

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

Apr. 20-22, 2014 Only critical and major patches committed Apr. 23, 2014 Drupal 8.0-alpha10 released. Emergency commits only. Apr. 24-27, 2014 Disruptive patch window
Categories: Planet Drupal

No Drupal core release on Wednesday, April 2

March 31, 2014 at 3:50am

The monthly Drupal core bug fix release window is scheduled for this Wednesday. The last Drupal 7 bug fix release was three months ago, but there haven't been enough changes to the development version since then to warrant a new release. As a result, there won't be a Drupal 7 bug fix release this month. A bug fix release next month (in May) is likely.

Upcoming release windows include:

  • Wednesday, April 16 (security release window)
  • Wednesday, May 7 (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.

Categories: Planet Drupal

Feedback needed: implementation plan for automatic entity schema generation

March 20, 2014 at 12:08am

We have an open critical beta blocker issue that aims to make the entity storage controller able to automatically generate the entity schema for all defined fields.

An initial implementation plan was laid out in Prague (see section Unify Field storage). I am going to work on it the next week at DDD Szeged and I sketched a more detailed plan of attack at:

https://drupal.org/comment/8552811#comment-8552811

Feedback is badly needed so that I don't waste a full week of sprint time working on something that might not be good enough (or at all).

Feeback especially welcome from @chx since there are some aspects that might be controversial, if I recall correctly his position. Moreover I need help figuring out how the proposed solution would play with Mongo.

Categories: Planet Drupal

Drupal core security release window on Wednesday, March 19

March 17, 2014 at 3:34am
Start:  2014-03-19 (All day) America/New_York Sprint Organizers:  David_Rothstein

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

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 release on this date; the next window for a Drupal core bug fix release is Wednesday, April 2.

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 Week-ish in Drupal Core: March 12, 2014

March 12, 2014 at 9:42pm
What's new with Drupal 8?

Two big news items this week for our intrepid testbots! First, RTBC core patches are now automatically retested every 24 hours to ensure they don't go stale and to avoid regressions and commit conflicts. Hooray!! Additionally, the 8.x testbots have been upgraded to PHP 5.4, which means Drupal 8 now officially requires PHP 5.4.2 or above to install. Woot! In addition to this allowing us to remove some legacy cruft regarding magic quotes and other things that are no longer relevant in PHP 5.4, there is also active discussion going on about how best to use 'traits', a new languge feature of PHP 5.4. Upgrade your dev environments accordingly!

Major headway was also made in removing the legacy router system, with the commit of Issue #2107533 by tim.plunkett, dawehner, pwolanin, Berdir: Remove {menu_router} -- a major milestone for the beta release, and anecdotally a big reduction in automated test times -- and Issue #2177041 by dawehner, Berdir, jibran: Remove all implementations of hook_menu. This thankfully resolves a rather confusing situation in alpha 9 where both hook_menu() and hook_menu_links_default() existed at the same time, duplicating each others' code.

Speaking of alphas, Drupal 8 alpha 10 is coming up on March 19! Here's the commit schedule around then: https://groups.drupal.org/node/412343

Drupal 8's migration path is making great headway in the sandbox, and with a two new maintainers and an initial patch to update the migrate API with the latest changes (note: this patch is both huge and needs reviews!) the hope is that the bulk of the Drupal 6 => Drupal 8 migration path will land soon!

And in BREAKING news, just as this was being posted, Issue #2148255 by jhodgdon: Make better D8 api.d.o landing page and put it in Core was committed, which now makes the Drupal 8 API landing page look like this:

Freshly organized, topic-based approach to introducing Drupal's APIs

Hot damn! Headings and stuff! Of course, now we need to actually write the docs behind those links. ;) If that sounds like a fun way to learn Drupal 8 to you, check out the child issues here: https://drupal.org/node/2148255

And finally, headed to DrupalCon Austin? Check out the Drupal 8 extended sprint schedule for DrupalCon Austin and book your travel plans accordingly!

Where's Drupal 8 at in terms of release?

Overall, beta blockers continue on a downward trend, with a big dip over the past two weeks, although beta targets are increasing as various issues get de-scoped from holding up beta1. Missing change records remain relatively flat-lined. It'd be great to have those cleaned up once and for all so we can stop tracking them. :D

Beta blockers moved from 50 to 35 in the past month, beta targets grew from 35 to 61, missing change records keep fluctuating around 13-14.

In terms of the overall Drupal 8 release, here's what our trajectory on all critical issues across the board looks like:

Trend line still continuing downwards from its peak in Sept. 2013, currently standing at 120 outstanding issues

Last week, we fixed 4 critical issues and 12 major issues, and opened 6 criticals and 4 majors. That puts us overall at 120 release-blocking critical issues and 483 major issues.

2 beta-blocking issues were fixed last week. There are still 36 of 121 beta blockers that must be resolved and 13 change records that must be written before we can release a Drupal 8 beta.

Where can I help?

Top criticals to hit this week

Each week, we check with core maintainers and contributors for the "extra critical" criticals that are blocking other work. These issues are often tough problems with a long history. If you're familiar with the problem space of one of these issues and have the time to dig in, help drive it forward by reviewing, improving, and testing its patch, and by making sure the issue's summary is up to date and any API changes are documented with a draft change record.

  • [meta] CMI path to beta has several really thorny child issues that are the most likely to hold release of beta 1, so all hands are needed on deck to help move these issues forward. The most important issue at the moment is #2201437: [META] Config overrides and language. Help by reviewing the sub-issues and the overall proposed architecture.
Notable Commits

The best of git log --since "2014-02-21" --pretty=oneline (197 commits in total):

In addition to the commits mentioned at the opening paragraphs, here are other big things folks have been working on:

You can also always check the Change records for Drupal core for the full list of Drupal 8 API changes from Drupal 7.

Drupal 8 Around the Interwebs

Blog posts about Drupal 8 and how much it's going to rock your face.

Drupal 8 in "Real Life"
  • March 24 - 30: Drupal Developer Days Szeged is coming up fast! In addition to many other sessions and sprints, you'll find Drupal 8 Module upgrade workshop as well as a sprint to get beta 1 out the door. Come join the festivities with some of the top Drupal 8 contributors!
  • Mar. 28 - 30: If you'd like to collaborate with DevDays Szeged sprinters, but are looking for something in the western hemisphere, check out MidCamp. MidCamp is March 28-30, and there may also be a pre-sprint March 26-27. Contact ZenDoodles for more information.
  • April 10 - 13: A bit further out, NYC Camp looks to also be a large Drupal event with a Drupal Core Summit and a variety of Drupal 8 sprints.
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.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. Contact xjm if you'd like to help communicate all the interesting happenings in Drupal 8!

AttachmentSize Screen Shot 2014-03-12 at 1.59.39 PM.png113.68 KB better_beta.png30.38 KB feb_outstanding.png25.21 KB
Categories: Planet Drupal

Drupal 8 alpha 10 on Mar. 19

March 5, 2014 at 6:20pm

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

Mar. 16-18, 2014 Only critical and major patches committed Mar. 19, 2014 Drupal 8.0-alpha9 released. Emergency commits only. Mar. 20-23, 2014 Disruptive patch window (just prior to Drupal Dev Days Szeged)
Categories: Planet Drupal

Join the extended Drupal 8 sprints in Austin from May 31st through June 8th!

March 4, 2014 at 5:28pm

We have a great tradition of extended sprints around big Drupal events including the ones we did around DrupalCons in Prague, Portland, Munich, Denver, as well as Drupal Dev Days like Szeged, Dublin and Barcelona. While there is a sprint day included in DrupalCons (usually) on Friday, given that a lot of the Drupal core and contrib developers fly in for these events, it makes a lot of sense to use this opportunity to start sooner and/or extend our stay and work together in one space on the harder problems.

DrupalCon Austin is next up! DrupalCon and the Drupal Association continue to recognize the need for extended sprints as part of the schedule and are providing space on Monday, and helping organize space for the weekends before and after also! We are still looking for additional sponsors for the weekend sprints before/after to help with coffee, tea and maybe food.

Travel Plans

Now is the time to consider if you can be available and book your travel and hotel accordingly!

Practical details

Dates
May 31st (Sat), June 1st (Sun), and June 7th (Sat) and 8th (Sun). (There is already a DrupalCon sprint day on Monday June 2nd and Friday June 6th 2014 at the DrupalCon venue as well).
Times
We start each day at 9am and have space booked until midnight.
Locations
Sign up, join the fun

Sponsors

Lead sponsor: Drupal Association

Looking for sponsors

We are looking for more sponsors to be able to pay for extra expenses. If you are interested sponsoring or if you need sponsors to cover expenses, please contact me at https://drupal.org/user/258568/contact

#node-310893 .picture, #node-310893 h3 { display: none; } #node-310893 .field-type-datestamp { margin: 0 0 2em 0; } #node-310893 dl { margin-bottom: 1em; } #node-310893 dd { margin-top: 0.5em; } #node-310893 h3.content { display: block; }
Categories: Planet Drupal

No Drupal core release on Wednesday, March 5

March 4, 2014 at 5:02am

The monthly Drupal core bug fix release window is scheduled for this Wednesday. However, the last Drupal 7 bug fix release was only two months ago, and we haven't yet had many changes to the development version since then. As a result, there won't be a Drupal 7 bug fix release in March.

Upcoming release windows include:

  • Wednesday, March 19 (security release window)
  • Wednesday, April 2 (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.

Categories: Planet Drupal

This fortnight in Drupal Core - February 21st 2014

February 21, 2014 at 10:41pm
What's new with Drupal 8?

This week (fortnight) saw the release of Drupal 8 alpha 9. Each release brings us that little bit closer to a beta. Some of the highlights from this fortnight include:

  • Remove all Simpletest overrides and rely on native multi-site functionality instead - issue 2171683. With this, each test run creates its own site inside sites/simpletest - eg sites/simpletest/13455678 - with its own settings.php and some apache files for security sake. This means that our testing is running in a real site, instead of a psuedo site with overloaded globals and various other workarounds.
  • The direct callability of theme() was removed in favor of building render arrays consistently. It has been renamed to _theme() and is for internal use only. Build render arrays instead of using _theme() in your code so you don't break caching, assets and JavaScript states, amongst other things. For more information see the change record.

And speaking of change records, just a reminder to check your patches for API changes and be sure to write your change record, these are now required before the issue is committed.

Where's Drupal 8 at in terms of release?

Last week, we fixed 11 critical issues and 14 major issues, and opened 4 criticals and 9 majors. That puts us overall at 116 release-blocking critical issues and 484 major issues.

5 beta-blocking issues were fixed last week. There are still 51 of 124 beta blockers that must be resolved and 14 change records that must be written before we can release a Drupal 8 beta.

Where can I help?

Top criticals to hit this week

Each week, we check with core maintainers and contributors for the "extra critical" criticals that are blocking other work. These issues are often tough problems with a long history. If you're familiar with the problem space of one of these issues and have the time to dig in, help drive it forward by reviewing, improving, and testing its patch, and by making sure the issue's summary is up to date and any API changes are documented with a draft change record.

More ways to help

Notable Commits

The best of git log --since=2014-02-09 --pretty=oneline (159 commits in total):

  • Issue #2171683 by sun, tstoeckler, larowlan: Remove all Simpletest overrides and rely on native multi-site functionality instead.
  • Issue #2147153 by dawehner, alexpott, Xano: Replace the last instance of $_GET/$_POST; Create a special exception listener / exception controller which allows to use POST requests - brings us closer to complete use of the Symfony Request instead of Super globals.
  • Issue #2188595 by alexpott, jibran: Create a ConfigManager to be able to remove config.inc - one less inc file..
  • Issue #2190643 by Berdir, amateescu, Xano, yched: Serializing the container is a very very bad idea, let's prevent it?.
  • Issue #2176065 by EclipseGc: Introduce a composer.json for Drupal\Component\Utility. Drupal being a good PHP Citizen.
  • Issue #2028025 by David Hernández, Berdir, larowlan, ceng, YesCT, a_thakur: Expand CommentInterface to provide methods - provides a much better DX
  • Issue #2193521 by sun, alexpott: Simpletest suffixes are not guaranteed to be unique. Finally, all those annoying "base table or view not found" random testbot failures will go away.

You can also always check the Change records for Drupal core for the full list of Drupal 8 API changes from Drupal 7.

Drupal 8 Around the Interwebs

Blog posts about Drupal 8 and how much it's going to rock your face.

Drupal 8 in "Real Life"
  • Feb. 28 - Mar 2: Two events happening simultaneously, DrupalCamp Phoenix and DrupalCamp London have some nice Drupal 8 session proposals, including CMI, multilingual, and more!
  • March 8-9:Florida Drupal camp is aiming to shine a spotlight on Drupal 8. Including several sessions on Drupal 8 and a Drupal 8 code sprint, should be lots of fun in a sunny location.
  • Mar. 24 - 30: Drupal Developer Days Szeged is going to be the Drupal 8 event of the next months, with a full week of sprinting awesomeness and lots of D8 content. See Five good reasons to register for Drupal Dev Days Szeged now by Gábor Hojtsy for more details.
  • Mar. 28 - 30: If you'd like to collaborate with DevDays Szeged sprinters, but are looking for something in the western hemisphere, check out MidCamp. MidCamp is March 28-30, and there may also be a pre-sprint March 26-27. Contact ZenDoodles for more information.
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.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. Contact xjm if you'd like to help communicate all the interesting happenings in Drupal 8!

Categories: Planet Drupal

[policy, no patch] Exempt migrate_drupal from coding standards

February 16, 2014 at 9:43am

This suggestion is made at https://drupal.org/node/2197431

Categories: Planet Drupal

Drupal core security release window on Wednesday, February 19

February 15, 2014 at 12:14am
Start:  2014-02-19 (All day) America/New_York Sprint Organizers:  David_Rothstein

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

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 release on this date; the next window for a Drupal core bug fix release is Wednesday, March 5.

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 alpha 9 on Feb. 19

February 11, 2014 at 9:54pm

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

Feb. 16-18, 2014 Only critical and major patches committed Feb. 19, 2014 Drupal 8.0-alpha9 released. Emergency commits only. Feb. 20-24, 2014 Disruptive patch window
Categories: Planet Drupal

This fortnight in Drupal core: February 8, 2014

February 8, 2014 at 10:08pm
What's new with Drupal 8?

It's been a remarkable couple of weeks for Drupal 8, with several landmark changes, a global sprint, and a surge in core issue queue activity.

Global sprint weekend

The second Global Sprint Weekend was held January 25-26. Over 400 sprinters participated at 39 locations on six continents, with others participating remotely in IRC. Some quick core issue queue statistics from the sprint timeframe:

  • 80 new core issues created
  • 553 patches submitted
  • 2468 comments posted on 646 issues
  • 113 issues RTBCed

A huge thanks to everyone who participated, and especially to the sprint organizers and mentors who helped make it happen.

Removal of the variable subsystem

A tombstone for variable_get(), variable_set(), variable_delete(), and the {variable} table.
Right on the heels of the Global Sprint Weekend, the last patch to convert variables to config or state was committed, and within a day the old variable subsystem was removed. This was the culmination of a year and a half of work by more than 80 contributors, and an incredible milestone for the Configuration Management Initiative.

Removal of the 7.x to 8.x upgrade path

At DrupalCon Portland, core maintainers agreed to stop using update.php for major version upgrades in favor of providing data migration from Drupal 7 (and Drupal 6!) with Migrate in core. So, last week we fixed Issue #2168011: Remove all 7.x to 8.x update hooks and disallow updates from the previous major version. Now the core codebase is as committed to Migrate as we are. ;) See Drupal 7 sites can no longer be upgraded to Drupal 8 with update.php for more information.

Now that hook_update_N() implementations will no longer be added for data model changes from Drupal 7, core patch contributors should keep an eye out for patches that might require migration updates instead. For details, read: No more 7.x to 8.x hook_update_N() -- file Migrate issues instead.

Change record drafts

It's now possible to create drafts of API change records, and a draft change record will be required before any API change is committed starting February 14. More information on the new feature and change record process: Change records now needed before commit.

On January 31, in preparation for this change, core contributors reduced the missing change record count from 40 to 20 in 24 hours. We actually halved this long-outstanding documentation debt within a single day. Amazing work!

Theme system conversions

Core theme system contributors have been busy the past several weeks, converting numerous theme functions to Twig and removing all calls to theme() outside drupal_render() (and some automated tests). This important theme system cleanup has been ongoing for more than seven months and blocks a beta release.

Additionally, after lots of work on these issues, joelpittet joined the theme subsystem maintainer team. Thanks Joel!

Where's Drupal 8 at in terms of release?

Last week, we fixed 14 critical issues and 24 major issues, and opened 5 criticals and 16 majors. That puts us overall at 132 release-blocking critical issues and 473 major issues.

11 beta-blocking issues were fixed last week. There are still 51 of 115 beta blockers that must be resolved and 12 change records that must be written before we can release a Drupal 8 beta.

Here's a quick look at our progress on criticals and beta blockers in January:

A graph showing the number of critical issues posted and fixed each month since September.
We tied our previous record of 48 criticals fixed within a single month, but this time while posting fewer new ones than that. ;) Great work!

A graph showing the issue counts for outstanding and fixed beta blockers week to week in January, as well as beta targets and change records.
We fixed a grand total of 37 beta blockers in January, putting us past the halfway point for the beta! We also made great progress on cleaning up the API documentation debt of our outstanding change records -- from over 50 at the start of the month to 19 at the end (and just 12 as of today)! That said, we also identified 20-odd additional beta-blocking issues over the course of the month, so it's important to keep our focus on these top-priority issues.

Where can I help?

Top criticals to hit this week

Each week, we check with core maintainers and contributors for the "extra critical" criticals that are blocking other work. These issues are often tough problems with a long history. If you're familiar with the problem space of one of these issues and have the time to dig in, help drive it forward by reviewing, improving, and testing its patch, and by making sure the issue's summary is up to date and any API changes are documented with a draft change record.

More ways to help

Notable Commits

The best of git log --after=2014-01-24 --pretty=oneline (191 commits in total):

  • Issue #2099741 by Wim Leers, wwalc, mr.baileys, eaton, dstol, nod_, effulgentsia: Protect WYSIWYG Editors from XSS Without Destroying User Data.
  • Issue #2183923 by tim.plunkett: Break the circular dependency in EntityManager.
  • Issue #2157053 by alexpott, twistor, dawehner, sun: Ensure register_shutdown_function() works with php-fpm (blocks testbot php-fpm).
  • Issue #1939064 by joelpittet, pwieck, farrington, mark.labrecque, Cottser, InternetDevels, mdrummond, drupalninja99, BarisW, jenlampton: Convert theme_links() to Twig.
  • Issue #1939062 by steveoliver, mdrummond, jenlampton, hussainweb, Cottser, joelpittet, jerdavis, ekl1773, dale42, drupalninja99, gabesullice, c4rl: Convert theme_item_list() to Twig.
  • Issue #2168011 by xjm, jessebeach, Damien Tournoud, znerol, Xano: Remove all 7.x to 8.x update hooks and disallow updates from the previous major version.
  • Issue #2167641 by tim.plunkett: EntityInterface::uri() should use route name and not path.
  • Issue #2164827 by Berdir, Xano, tim.plunkett: Rename the entityInfo() and entityType() methods on EntityInterface and EntityStorageControllerInterface.
  • Issue #2167623 by danilenko_dn, sidharthap, Nitesh Sethia, krishnan.n, aitiba, alexpott, ashwinikumar, Barrett, damiankloip, deepakaryan1988, foxtrotcharlie, ianthomas_uk, neetu morwani, nonsie, piyuesh23, Sharique, sivaji, sushantpaste, swentel, vijaycs85, YesCT: Add test for all default configuration to ensure schema exists and is correct.
  • Issue #2177739 by Berdir, alexpott, Gábor Hojtsy: Fix inefficient config factory caching.
  • Issue #2047633 by pwolanin, dawehner, kim.pepper, Xano, amateescu, tim.plunkett: Move definition of menu links to hook_menu_link_defaults(), decouple key name from path, and make 'parent' explicit.
  • Issue #2164367 by alexpott, tim.plunkett, dawehner: Rebuild router as few times as possible per request.
  • Issue #2167109 by Berdir, sun, alexpott, ACF, acrollet, adamdicarlo, Albert Volkman, andreiashu, andyceo, andypost, anenkov, aspilicious, barbun, beejeebus, boombatower, cam8001, chriscalip, chx, cosmicdreams, dagmar, damiankloip, dawehner, deviance, disasm, dixon_, dstol, ebrowet, Gábor Hojtsy, heyrocker, Hydra, ianthomas_uk, japicoder, jcisio, jibran, julien, justafish, jvns, KarenS, kbasarab, kim.pepper, larowlan, Lars Toomre, leschekfm, Letharion, LinL, lirantal, Lukas von Blarer, marcingy, Mike Wacker, mrf, mtift, mtunay, n3or, nadavoid, nick_schuch, Niklas Fiekas, ParisLiakos, pcambra, penyaskito, pfrenssen, plopesc, Pol, Rok Žlender, rvilar, swentel, tim.plunkett, tobiasb, tsvenson, typhonius, vasi1186, vijaycs85, wamilton, webchick, webflo, wizonesolutions, xjm, yched, YesCT, znerol: Remove Variable subsystem.

You can also always check the Change records for Drupal core for the full list of Drupal 8 API changes from Drupal 7.

Drupal 8 Around the Interwebs

Blog posts about Drupal 8 and how much it's going to rock your face.

Drupal 8 in "Real Life"
  • Feb. 14 - 17: Drupal South in Wellington, New Zealand features a keynote by Larry Garfield of WSCCI fame, larowlan and kim.pepper answering everything you you wanted to know about Drupal 8 but were afraid to ask, as well as sessions on Twig, Tour, and more!
  • Feb. 28 - Mar 2: Two events happening simultaneously, DrupalCamp Phoenix and DrupalCamp London have some nice Drupal 8 session proposals, including CMI, multilingual, and more!
  • Mar. 24 - 30: Drupal Developer Days Szeged is going to be the Drupal 8 event of the next months, with a full week of sprinting awesomeness and lots of D8 content. See Five good reasons to register for Drupal Dev Days Szeged now by Gábor Hojtsy for more details.
  • Mar. 28 - 30: If you'd like to collaborate with DevDays Szeged sprinters, but are looking for something in the western hemisphere, check out MidCamp. MidCamp is March 28-30, and there may also be a pre-sprint March 26-27. Contact ZenDoodles for more information.
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.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. Contact xjm if you'd like to help communicate all the interesting happenings in Drupal 8!

Categories: Planet Drupal

No more 7.x to 8.x hook_update_N() -- file Migrate issues instead

January 31, 2014 at 11:25pm

At DrupalCon Prague, we decided not to provide a Drupal 7 to Drupal 8 upgrade path using the database update system, and to instead provide data migration using a Drupal 8 data migration API based on the Migrate module. As of today, Drupal 7 sites can no longer be upgraded to Drupal 8 with update.php, and all implementations of hook_update_N() have been removed from Drupal 8 core.

Going forward, hook_update_N() should only be included to provide 8.x to 8.x updates, once the 8.x to 8.x upgrade path is supported.

If your patch introduces a data model change that would previously have required a hook_update_N() implementation, consider instead whether a new / changed data migration is needed. Migration works by calling APIs, so most changes (for example entities) are covered already. But if your data change is not covered by an API (like changing a raw configuration object name or key) then you need to:

  1. Create a new issue in the Migrate component.
  2. Document the data model change in the issue and reference the core issue that introduces it under the "related issues" section.
  3. Update the summary of your main issue to indicate that the data model change has a corresponding Migrate issue.

If you are unsure whether new migration code is needed, file the issue anyway, and Migrate maintainers will review it and close it if it is not needed.

Categories: Planet Drupal

No Drupal core release on Wednesday, February 5

January 31, 2014 at 8:45pm

The monthly Drupal core bug fix release window is scheduled for this Wednesday. However, the last Drupal 7 bug fix release was only a month ago, and I also won't be available next week to coordinate a release. As a result, there won't be a Drupal 7.x bug fix release in February.

Upcoming release windows include:

  • Wednesday, February 19 (security release window)
  • Wednesday, March 5 (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.

Categories: Planet Drupal

Pages