Core

Drupal core major happenings and opportunities to contribute are announced in this group, please follow the RSS feed to learn about these.

Posting to this group is restricted to people listed in MAINTAINERS.txt. If you have an announcement you'd like to post in this group, please file a webmasters issue with the suggested text and for quicker attention paste a link to that issue in #drupal-contribute.

David_Rothstein's picture

No Drupal core release on Wednesday, February 5

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)
Read more
xjm's picture

Change records now needed before commit

Starting February 14, issues that require API change records must have these change records written before patches are committed. This is Drupal 8 core's valentine to contributed modules. :)

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
jessebeach's picture

We still have numerous "fixed" D8 issues that cannot be closed until a Change Record is published

Two weeks ago I wrote that we had 40 "fixed" issues that cannot be closed until a change record is published for them.

Read more
Gábor Hojtsy's picture

The biggest Drupal core sprint and developer camp is coming up in March!

Drupal Developer Days 2014 is coming up quick in Szeged, Hungary from March 24th (Mon) to the 30th (Sun) 2014. Szeged, Hungary may sound like it is the middle of nowhere but what do you need to get together with a bunch of Drupal developer friends and learn about and advance the platform together? As those who have been to DrupalCon Europe 2008 in the same city know, Szeged is the ideal place for just that. Check out our interviews about those experiences.

Here are some quick facts about Drupal Dev Days 2014:

  • A whole week of sprints with two core committers (Alex Pott and Nathaniel Catchpole) as well as the testbot system maintainer (Jeremy Thorson) on location! Could we help more to make progress? Oh, most top European Drupal developers are already signed up to come as well!
  • Three days of sessions and workshops (50 topics providing 56 hours of content). Get lots of readily applicable know-how including website monitoring, e-commerce, practical scrum, Vagrant, product development in real life, Heisencache, IDE tricks and so on. Look into how Drupal is made, see the life of a core maintainer, get gamification tips or discuss a new type of money: Druplicoins!
  • Want to work on upgrading your modules to Drupal 8 but don't know how? No problem! Additionally to learning about all the new Drupal 8 subsystems, there is a bring-your-own-module workshop as well, where mentors will help you upgrade your module!
  • Want to get into Drupal development? Attend the community tools workshop and learn all the tools we use to communicate and work on solutions and learn and enjoy how the Drupal mentoring program works.

A truly fantastic opportunity isn't it? Last but not least its also very cheap. The ticket is only 30 Euros for the whole week! If you want to get to know Drupal 8 or even help make it happen, this is the place to be in March. Note that some cheap hotel deals expire this week. Don't miss out!

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
David_Rothstein's picture

Drupal core security release window on Wednesday, January 15

Start: 
2014-01-15 (All day) America/New_York
Organizers: 

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

This does not mean that a Drupal core security release will necessarily take place on that date for either the Drupal 6 or Drupal 7 branches, only that you should prepare to look out for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release).

There will be no bug fix release on this date; the next window for a Drupal core bug fix release is Wednesday, February 5.

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
jessebeach's picture

Let's focus down on automated accessibility testing; working with the Dutch to make it happen

I mentioned in the recap of the Green by 2014 initiative that I've been working to organize a follow-on effort to continue building our automated accessibility testing tools. I just published the announcement at the following URL.

https://medium.com/p/c1a3a275fe1a

Here's the title and sub-title:

"Open-source accessibility testing for the modern web"

"Collaborating to improve Quail, an open-source web accessibility testing tool that will integrate with existing continuous integration processes and developer toolchains."

Read more
xjm's picture

D8 alpha 8 on Jan. 22; new commit schedule for Drupal 8 alpha releases

To improve core momentum as we work toward a Drupal 8 beta, we are going to try some added structure in the commit schedule around Drupal 8 alpha releases:

  1. For several days before each alpha release, we will commit only critical and major patches, to encourage focus on these important issues in preparation for each alpha release. (See the documentation on core issue priorities for more information.)

  2. Immediately following the alpha release, there will be "disruption days". Core maintainers will work with patch authors to schedule commits for patches that are difficult to reroll or are likely to break many other patches (for example, patches that touch dozens of files, or make significant changes to key APIs). The goal here is to help contributors know when to reroll these patches for the best chance of a timely commit, and to manage conflicts with critical, major, and beta-blocking issues. Patches that should be scheduled are identified at the core maintainers' discretion. See the Avoid commit conflicts and Will cause commit conflicts issue tags.

Read more
jessebeach's picture

Learn more about Drupal 8 and help the wider Drupal community by writing up a Change Record

A happy 2014! What a great year for a Drupal major release!

Have you started learning the new Drupal 8 APIs? Are you porting your modules forward to an 8.x branch? Are you a curious site builder ready to adopt the new hotness that will be Drupal 8?

Read more
David_Rothstein's picture

Drupal 7 core release on Wednesday, January 1 (or Thursday, January 2)

Start: 
2014-01-01 (All day) - 2014-01-02 (All day) America/New_York
Organizers: 

The monthly Drupal core bug fix release window is this Wednesday, and since it has been a while since the last one, I plan to release Drupal 7.25 on that date. However, in practice the release might not happen until Thursday, due to the holiday and to give people a bit more time to test the latest code. Per our release policy, this will be a bug fix release only (no security fixes).

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
Gábor Hojtsy's picture

Join us for a week of Drupal 8 in March!

Drupal Developer Days 2014 is coming up quick in Szeged, Hungary from March 24th (Mon) to the 30th (Sun) 2014. Szeged, Hungary may sound like it is the middle of nowhere but what do you need to get together with a bunch of Drupal developer friends and learn about and advance the platform together? As those who have been to DrupalCon Europe 2008 in the same city know, Szeged is the ideal place for just that. Check out our interviews about those experiences.

This is not only the event to come to if you want to learn about Drupal 8 but also to get involved with Drupal (core) development. If you are not a contributor yet we plan to have plenty opportunities to help get you on board. If you know what you want to work on, we'd love to get out of your way and provide you with all the pieces needed for you to work on outstanding Drupal 8 core issues. We expect hundreds of developers to attend this event, and core development involvement is not at all a requirement. However, if you are eager to help out, this is a great chance! This is the biggest continuous sprint of the year to help get Drupal 8 closer to release!

If you are just considering taking a deeper look at Drupal 8, this is the ideal event for you with hands-on workshops as well as key Drupal developers on location to work with to fix issues that bug you.

Our tickets start at just 30 EUR and we also offer scholarships! We now accept presentation and workshop submissions as well as code sprint suggestions and signups! Let's explore and advance Drupal 8 together!

Ps. We are looking for sponsors to help put on the event and sponsor key Drupal core developers to attend! This is a great time to show your company's commitment to Drupal 8.

Read more
chx's picture

No Drupal Core security release on December, 18th, 2013

As seen on https://twitter.com/drupalsecurity/status/413348144714616832 there will be no core security release today.

Gábor Hojtsy's picture

Drupal 6 to stop supporting PHP 4 on March 1st 2014

Drupal 6.0 was released almost 6 years ago in February 2008. The Drupal community is committed to release Drupal 6 bugfixes until Drupal 8.0 is released and with recent changes provide security fixes much longer.

The hosting and development landscape was very different in 2008 though. PHP has gone a long way since we released Drupal 6. While Drupal 6 is still supported on PHP 4.x, the PHP developer community itself end-of-lifed PHP 4 just half a year after Drupal 6.0 came out. According to public statistics and data available to us about Drupal 6 sites, we estimate that there is a very small number of Drupal sites which may still run on PHP 4. We also don't believe it is in our best interest to support Drupal 6 on a possibly insecure but definitely unsupported base system, so we discussed and decided to drop support for PHP 4 on March 1st 2014.

If you are running a Drupal 6 site on PHP 4.x, we suggest you look at your hosting situation as it is likely there are other outdated (and possibly insecure) components involved in your environment as well. For the secure operations of your site, we suggest you look at other hosting options. We suggest to look for hosting with at least PHP 5.2.4 (same as Drupal 7's oldest supported PHP version).

While we don't plan to deliberately introduce PHP 5 constructs in Drupal 6, this change also lets contributed module developers to use PHP 5 more easily in their code.

Read more
David_Rothstein's picture

Drupal core security release window on Wednesday, December 18

Start: 
2013-12-18 (All day) America/New_York
Organizers: 

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

This does not mean that a Drupal core security release will necessarily take place on that date for either the Drupal 6 or Drupal 7 branches, only that you should prepare to look out for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release).

There will be no bug fix release on this date; the next window for a Drupal core bug fix release is Wednesday, January 1.

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

Tour Module Scrum

Start: 
2013-12-06 10:00 - 10:15 Australia/Brisbane
Organizers: 

We're getting to the point in the Drupal 8 cycle where the UI's are starting to solidify and we have fairly static markup to write interface tours against.

So to facilitate this, we're going to have a weekly scrum to coordinate pain points, progress and participants.

If you're interested in helping write tours for the Drupal 8 UI or identify and resolve any remaining API issues, please come along to this short meeting (Google hangout).

Read more
webchick's picture

This (two!) weeks in Drupal Core: December 4, 2013

What's new with Drupal 8?

The last two weeks have been absolutely ACTION PACKED Drupal 8 core-wise. Let's see if I can remember it all. :)

Migrate in core

The Migrate in Core team had their first core patch land! This provides the underlying architecture for migrations, as well as a variable-to-CMI migration as a proof of concept. Drupal 8 will provide migrations from Drupal 6 and Drupal 7 both. If you're curious to see how it works, read the change notice for a quick overview, and the excellent documentation for more details. BIG congrats to mikeryan, chx, marvil07, bdone, jessehs, mpgeek, BTMash, fastangel, mongolito404, Moshe Weitzman, eliza411, YesCT, dawehner, and cosmicdreams!

RIP Overlay

Ding, dong! Overlay module is dead! My ears are still ringing a bit from all of the cheers and applause. :P~ However, rather than the module simply being booted to /dev/null, it has instead been replaced by a nifty "Back to site" button that shows up when you're in an admin context, and takes you back to where you were on your main site:
When on an admin page, a 'Back to site' link appears in the top left portion of the toolbar.
After extensive usability testing, this solution was found to solve the same "lost context" problem as the Overlay, but with a few thousand fewer lines of code. :) Let us all build nod_ a statue, as well as yoroy, lisarex, and Bojhan from the UX team.

Help fund a Drupal 8 core maintainer

Alex Pott, single-handedly responsible for almost 50% of the commits in Drupal 8 since he became a core maintainer, is nearing the end of his savings account + Gittip supplements that have allowed him to focus on core full time the past few months. Alex is actively seeking diverse community funding to sustain his momentum independently. If you're a business excited about the new awesome things Drupal 8 will bring, this would be an excellent way to very directly support all of D8 contributors' efforts.

Drupal 8 Alpha 6

drupal 8.0-alpha6 shipped, and alpha 7 is due on December 16. Get your patches in now! Here's the current hit-list.

Drupal security releases

There were also security releases of Drupal 6 and 7, which we are are in the process of forward-porting to Drupal 8 now. If you can help here to ensure expedient patching, that would be great!

Where can I help?

Read more
Subscribe with RSS Syndicate content

Core

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week