Add new comment

This week in Drupal core: December 19, 2013

Bonjour, it is that time of year again, we hope that you are getting ready for the holidays and New Year. If not, then we are ready with final edition of This Week in Drupal Core of 2013! :)

What's new with Drupal 8?

A new D8 alpha

Drupal 8.0-alpha7 was released today! Download it, try it out, and explore the latest-and-greatest in Drupal 8. There will be a new alpha release come mid-January. Watch this spot for more details!

PHP 4 support EOL in D6

As part of efforts to improve the core release cycle, support data migration from Drupal 6 to Drupal 8 (join up here!), and make best use of our limited security team resources, we've decided to stop supporting PHP 4 for Drupal 6 as of March 1, 2014.

Last week's top criticals

Two of last week's top criticals have been fixed thanks to everyone's focused efforts!

Theme negotiation

A new theme negotiator service is added to replace 'theme callback' form hook_menu() and move us closer to removing the legacy menu and routing technical debt. Thanks dawehner, David Rothstein, and tim.plunkett!

Where's Drupal 8 at in terms of release?

In the past week, we've fixed 9 critical issues and 5 major issues, and opened 1 critical and 12 majors. That puts us overall at 115 release-blocking critical issues and 488 major issues.

So what's the big picture? How long is it going to take to release Drupal 8.0? Here's a look at the criticals we've opened versus fixed each month since API freeze on July 1:

Critical issues posted and fixed. In July 2013, many more criticals were posted than were fixed, but now many more are fixed than posted!
Since September, we are consistently resolving more critical issues than we file each month. This is exactly what needs to happen during this point in the release cycle. (Keep in mind that December is still in progress!)

Taking a wider view at the history of Drupal 8, here's the trend of our outstanding critical technical debt since the 8.x branch was opened in March 2011:

Outstanding critical issues. The number increases steeply starting in Sept. 2012, peaks in Aug. 2013, and has been dropping since.

Note that the number of critical issues is dropping steeply -- hooray! -- but there's also still a very long way to go. We need to reduce our technical debt more quickly for a mid-2014 release. To this end, please help us by focusing only on the most important issues, avoiding unnecessary and disruptive changes, and leaving nice-to-haves for Drupal 8.1 or later. (Read more about how we're improving the Drupal 8 release cycle.)

* Observant Drupal 8 enthusiasts will notice that the above chart looks very different from drupalreleasedate.com. That's because we're only looking at the "true" (final) priority of issues, to filter out distortions from changes in core policy (e.g., when we recategorized outstanding change records from critical to major). The historical data comes from queries against the Drupal.org database.

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.

More ways to help

If core's toughest criticals aren't on your to-do list this week, there are lots of other places to jump in and help with conversions and cleanups in core. The Drupal 8 "meta meta", compiled by vijaycs85, is a great place to start if you want to dig your teeth into a technical problem but aren't sure where to start. Here are a few of the meta meta's metas (ha!) that are all important for finishing Drupal 8:

  • In our two-step process to convert core to the new routing system, we've completed the first step (removing the backwards-compatibility layer to the legacy routing system), but we still have lots of work to do to clean up our page controllers and remove unneeded page callbacks. These issues are a great way to learn about Drupal 8's routing system and become more familiar with Drupal 8's object-oriented paradigms and best practices.
  • Now that Views is in core, we're converting core listings to Views to make Drupal more customizable and to remove redundant, legacy code. If you can build a view, you can probably help review and test these issues! The conversions are also a great opportunity to learn about Drupal 8 features like the configuration system and the Plugin API.
  • After removing drupal_set_breadcrumb() from Drupal 8, now we are very close to removing drupal_set_title() as well. These issues are very important and will help in improving caching behavior in Drupal 8. Take a look and see if you can help cleaning up the remaining uses.

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 --since "1 week ago" --pretty=oneline (53 commits in total):

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

  • Jan. 25-26: Mark your calendars for the next Global Sprint Weekend. Join local user groups around the planet for a weekend of Drupal 8 contribution. The sprint weekend will be a great opportunity to engage your local community, and there are lots of resources on the sprint page to help get new people involved. Events are already planned everywhere from Illinois to Budapest to Montréal to Spain. Add yours today!
  • 24-30 March 2014: Drupal Developer Days Szeged: DevDays is still a ways off, but it will be the most important Drupal 8 developer event before DrupalCon Austin in June, so consider whether you can attend! See Join us for a week of Drupal 8 in March! by Gábor Hojtsy for more details.
  • DrupalCon Austin: Five Reasons We Are Excited About DrupalCon Austin: We all love DrupalCons and Drupal Association has shared some intresting facts about upcoming DrupalCon Austin.

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!

Also, just a reminder that This Week in Drupal Core is taking the next two weeks off for the holidays. See you again on January 8!

Attachment Size
issues-status.png 16.6 KB
outstanding-issues.png 29.03 KB

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.