This Week in Drupal Core

effulgentsia's picture

This week (or two or three) in Drupal Core

What's new with Drupal 8?

Configuration system changes

Over the past month, a lot of work has gone into the configuration system. With the addition of a separate module install/uninstall step for the config import process, it's finally possible to properly synchronize configuration changes with module installations or uninstallations. You can now transform a site installed with the Minimum install profile into a site using the Standard install profile by importing configuration (the case we've long said will be our indicator that CMI "works"). (Watch this screencast to see it in action!)

Additionally, after thorough discussion, the active storage for the configuration management system has been moved into the database by default. This means existing Drupal 8 sites will likely need to be reinstalled (or otherwise migrate the active configuration). Read the change record on active configuration in the database for details on why this decision was made.

Now is the time to start really testing CMI deployments. Spin up a dev site, make a copy of it, and test synchronizing complex configuration system changes between the two. See if the system behaves as you expect (and report the problems you find!) For an overview of the outstanding work being done on the configuration system, see #2187339: [meta] CMI path to beta.

NYC Camp at the United Nations

Camp attendees line up outside the UN, under the flags of many nations.
The third annual NYC Camp was held at the United Nations. (Yes, that United Nations, with the flags.) In addition to numerous sessions about Drupal 8 (check out fmitchell's session on 30 Drupal 8 API functions you should already know), we held several days of Drupal 8 core sprints. Media contributors also sprinted on Media for Drupal 8; read their sprint status report for more information. Finally, Drupal Association executive director Holly Ross worked on a Drupal 8 patch got her first Drupal core commit credit! Are you next? :)

Where's Drupal 8 at in terms of release?

We're in the last stretch of Drupal 8's alpha phase. We've fixed over 130 beta-blocking issues, including 9 in the last week, plus written more than 70 missing change records. The last 28 beta blockers include some difficult issues, but consider some of what we've already accomplished since the beginning of 2014:

  • The removal of the variable subsystem after 18 months.
  • The rearchitecture of configuration synchronization to support the minimum viable usecase after 16 months.
  • The removal of the legacy menu router after nearly a year.
  • The removal of widely used cache-breaking functions including drupal_set_title(), drupal_add_css(), drupal_add_js(), and theme().
  • The removal of all stale hook_update_N() implementations and the modification of update.php to require Migrate for major version upgrades instead.

(And of course so much more.)

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.

  • #2116363: Unified repository of field definitions (cache + API) converts remaining usages of the deprecated field info API to use methods from the entity manager, and is therefore critical to stabilizing the Entity Field API for the beta release. This significant (~150 KB) patch needs thorough code review from contributors familiar with Drupal 8's entity and field systems.

  • #2183231: Make ContentEntityDatabaseStorage generate static database schemas for content entities is an even larger (~250 KB) beta-blocking patch for the entity system that allows the entity system to automatically create the necessary database tables for entities, resolving numerous different issues. This is another significant change and needs lots of thorough review from as many people as possible.

  • #2198429: Make deleted fields work with config synch needs review of the patch's architecture and functionality. Deleting a field is a significant operation, because the site has to go on to purge all the field instance data for entities that have the field while leaving those entities intact. Drupal 7 includes a lot of code to support this functionality, and in Drupal 8, there's additional complexity since this purge needs to happen when a deleted field is staged and synchronized to another environment.

  • #2124749: [meta] Stop using request attributes as a storage mechanism for other services covers a collection of issues to improve the developer experience around Drupal 8's use of Symfony's request attributes (a public property on the request object that can be used for context-specific information about the request). This context information is not easily discoverable for contributed module developers, and, in some cases, using it adds to the apparent verbosity and complexity (e.g. in the replacements for the common D7 functions menu_get_object() and menu_get_item()). The numerous sub-issues for this meta issue are intended to weed out misuses of the request attributes and provide clear public APIs for others. Help discuss the developer experience and architecture in the numerous child issues for this meta.

More ways to help

Read more
mparker17's picture

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

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.

Read more
webchick's picture

This Week-ish in Drupal Core: March 12, 2014

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.
Read more
larowlan's picture

This fortnight in Drupal Core - February 21st 2014

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

Read more
xjm's picture

This fortnight in Drupal core: February 8, 2014

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 Drupal 8 core issues created
  • 553 Drupal 8 patches submitted
  • 2468 comments posted on 646 Drupal 8 issues
  • 113 Drupal 8 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 Prague, 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

Read more
effulgentsia's picture

This (two) weeks in Drupal Core

What's new with Drupal 8?

Last week, in lieu of a This week in Drupal Core, xjm and wechick compiled a phenomenal This YEAR in Drupal Core, so here's a catch up of the last two weeks.

Happy 13th birthday, Drupal!

Drupal 1.0.0 was released on January 15th, 2001. Many software projects from that era are long forgotten by now. That we have stayed relevant and gotten stronger through 13 years of fast and chaotic evolution of the internet is, in my opinion, very impressive. Here's some highlights from the birthday:

Drupal 8 Alpha 8

For module developers who've already begun porting their modules to Drupal 8, there's a shiny new alpha8 for you to play with as of yesterday. These alphas are provided to give you something more stable to work off of than having to chase HEAD every day. If you do choose to chase HEAD though, be prepared for more volatility. For example, Move definition of menu links to hook_menu_link_defaults(), decouple key name from path, and make 'parent' explicit was a very important patch committed immediately following the alpha8 release, but requires extensive follow up changes that we are trying to resolve between now and the next alpha.

Where's Drupal 8 at in terms of release?

Last week, we fixed 7 critical issues and 11 major issues, and opened 6 criticals and 20 majors. That puts us overall at 136 release-blocking critical issues and 497 major issues.

3 beta-blocking issues were fixed last week. There are still 60 of 107 beta blockers that must be resolved and 38 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.

More ways to help

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. Or if coding isn't your thing, there are plenty of issues tagged as Needs change notification. Writing these is a great way to keep abreast of recent changes - see more on change records to get started.

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.

Read more
webchick's picture

This YEAR in Drupal Core (2013)

Co-authored by xjm and webchick

Welcome! For Drupal's 13th birthday, in addition to Give Drupal a Birthday Present: Tackle a D8 Issue!, we wanted to celebrate the occasion with a retrospective of the year 2013 as it relates to Drupal core development!

Here are some stats to get us started:

  • 1,120 unique Drupal 8 patch contributors during 2013, bringing the total number of contributors for the release to over 1,800!
  • 4,175 Drupal 8 core patches committed (even with one core maintainer on leave for several months).
  • 316 critical issues fixed.
  • Nearly 10,000 automated test assertions added, bringing our total to nearly 60,000 tests!
  • Over 60,000 lines of documentation added (and for the record, less than 2% of our lines of documentation are {@inheritdoc}). :P

A tag cloud showing the top Drupal 8 contributors

A tag cloud showing the top Drupal 8 contributors
Photo credit: Wordle.net

Read more
larowlan's picture

This (three) weeks in Drupal Core - January 10th 2014

What's new with Drupal 8?

It's been three weeks since our last 'This week in core' post, but with holidays providing a welcome break for many, core development has continued at its usual rapid pace. Time flies! The session submission deadline for Drupal Dev Days Szeged is just around the corner on the 15th of January.

Give Drupal a birthday present

Next week is Drupal's 13th birthday! Want to give Drupal a birthday present? Why not tackle an issue, or help mentor someone else to do so. There's also a Reddit AMA appearance by Dries (that's Ask me anything for those who don't use Reddit - I had to look it up) and we're also planning a special "This Year in Drupal Core".

New Drupal core commit schedule

We're trying out a new commit schedule to increase core momentum. For one week starting January 15 up until the release of Drupal 8.0-alpha8 on January 22, core maintainers will commit only critical and major patches. (Normal and minor patches will be committed again starting January 23.) Read more about the new commit schedule.

Where's Drupal 8 at in terms of release?

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

10 beta-blocking issues were fixed last week. There are still 61 of 98 beta blockers that must be resolved and 48 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.

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. Or if coding isn't your thing, there are plenty of issues tagged as Needs change notification. Writing these is a great way to keep abreast of recent changes - see more on change records to get started.

Additionally:

  • The CMI initiative are planning to hold biweekly meetings to gain momentum around the remaining critical issues
  • 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.
Read more
jibran's picture

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.

Read more
xjm's picture

This week in Drupal core: December <del>11</del> 12, 2013

Sorry that we're a day late this week! If you'd like to reduce delays due to xjm's chronic insomnia, consider helping out with these posts. ;)

What's new with Drupal 8?

Working toward drupal-8.0-beta1

This week's most important Drupal 8 news is Dries' announcement of the criteria for beta 1. Numerous contributors worked with core maintainers to flesh out an initial list of beta-blocking issues, and many contributors have begun to work on core in a beta-bound mindset. We'll have more updates on our progress toward beta in upcoming weeks.

Looking for Drupal 8 API documentation?

Did you know that there's already extensive API documentation available for Drupal 8? The documentation is still under development since some APIs are still being finalized, but it's a great resource for developers who would like to explore Drupal 8. You can even help us extend the documentation as you learn. :) Gábor Hojtsy is leading efforts on this section of the handbook. (Also check out this quick guide to Converting 7.x modules to 8.x, also under development.)

Views block conversions

This week the patch for #1957276: Let users set the block instance title for Views blocks in the Block UI finally landed. This longstanding usability issue was blocking the conversion of legacy core blocks to Views -- an important step in realizing the full potential of Views in core. Now that it's in, the block conversions have begun in earnest! Thanks to the VDC team, yoroy, and Bojhan for driving this issue home, and to all contributors who are working on the conversions! To help, check out [Meta] Convert core listings to Views.

Where's Drupal 8 at in terms of release?

In the past week, we've closed 15 critical issues and 26 major issues, and opened 7 criticals and 15 majors. That puts us overall at 112 release-blocking critical issues and 475 major issues.

Where can I help?

Top criticals to hit this week

So, as I said above, we've got plenty of critical issues to go around. :) But here are a few super important ones we could use your help on right now.

Drupal 8 alpha 7 is due on December 16. Get your patches in now!

More ways to help

Testbot, testbot...

There's been a lot of demand on our awesome testbot volunteers jthorson and rfay for support for optional database environments (e.g. SQLite, PostgreSQL) and alternate PHP versions (especially PHP 5.4), as these are blockers for the D8 release. These features are currently blocked on some debugging tasks that could use your help! Set up a local testbot environment with Vagrant (see this helpful video) and head over to SQLite testbot confirmation fails with "failed to find test tables to drop" error and 6.x-3.x PIFR: 3 Failures in D8 test. These will allow us to make progress on Provide php 5.4 testing on testbots for D8 code without breaking everything else.

Drupal 8 performance

Performance optimization is among the most important ongoing work during Drupal 8's API completion phase. Follow [meta] Resolve known performance regressions in Drupal 8 for periodic updates on the work being done. We could also use help from one or more contributors to update this issue's summary to reflect the current work. The Drupal 8 performance team holds weekly meetings to discuss perfomance work, and manages performance issues in this spreadsheet of Drupal 8 performance issues. If you'd like to join these efforts, contact Moshe Weitzman.

Core mentoring

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.

Read more
Subscribe with RSS Syndicate content