Core

Drupal core major happenings and opportunities to contribute are announced in this group. Follow the RSS feed for these updates.

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.

Gábor Hojtsy's picture

Work on Drupal 8 at major core sprints, August 7-10

This summer is an important time to help get Drupal 8 done, so there is no good reason to skip getting together. We are holding two Drupal 8 sprints at the same time on August 7 to 10: one in North America at TCDrupal, and one in Europe at Drupalaton. Sprinters from both events will collaborate on Drupal 8 issues.

Join jthorson, xjm, alexpott, Crell, mtift, YesCT, and other lead Drupal 8 developers at Twin Cities DrupalCamp (North America) or dawehner, swentel, fago, Wim Leers, rteijeiro, lewisnyman, emma.maria and Gábor Hojtsy among others at Drupalaton (Europe). Read more in the event announcement.

Read more
webchick's picture

Tuesday, July 29: Drupal 8.0.x being branched for semantic versioning

Start: 
2014-07-29 12:00 - 14:00 America/New_York

On this date, the new 8.0.x branch for Drupal 8 will be created so we can start using the new Drupal release cycle in advance of beta 1.

Steps involved are:

  • drumm will create the 8.0.x branch
  • Existing issues will be moved automatically from 8.x-dev to 8.0.x-dev (this may take a couple of hours)
  • basic will patch Testbot to look at the new 8.0.x branch instead of the old 8.x branch.
Read more
larowlan's picture

Drupal core updates for July 16, 2014

What's new with Drupal 8?

This week saw the commit of part one and two of the major menu-system rewrite in which menu-links become plugins. The original patch weighed in at over 600kb and was one of the remaining seven beta-blockers. Splitting it into five separate issues made reviews more forthcoming and this was evident with part one and two moving quickly from needs review to RTBC to ultimately being committed. Reviewers have now moved onto parts three through five.
There was a massive volume of commits this week with cleanups keeping the committers very-busy, lots of deprecated functions were removed and lots of procedural menu and form code was ported to the new Object-oriented approaches.

Where's Drupal 8 at in terms of release?

In the past week, we've fixed 3 critical issues and 8 major issues, and opened 5 criticals and 9 majors. That puts us overall at 107 release-blocking critical issues and 623 major issues.

Outstanding beta blockers

Outstanding beta-blocking issues since January 2014, decreasing from 120 to only 7 now!

Outstanding critical issues in Drupal 8

Critical issue count in Drupal 8 since 2011, declining since July 2013

Outstanding major issues in Drupal 8

Major issue count in Drupal 8 since 2011, increasing steadily since September 2012

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, we could use your help!

More ways to help

Issue #1679344: Race condition in node_save() when not using DB for cache_field recently caused a Drupal.org outage. The issue already has a proposed resolution recommended in comment #24 — help out by reviewing the patch for either D7 or D8.

Additionally, there are a bunch of easy documentation issues which need some help moving forward. For each of these, there is a "Child Issues" sidebar. Look there for issues that are "active", "needs work", or "needs review":

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.

You can also help by sponsoring Drupal core development.

Read more
larowlan's picture

Core contact module roadmap

Background

Now that we have a new release cycle, we have the possibility of new features in minor releases, i.e. although we are in feature freeze for 8.0, that doesn't mean we can't add new features until 9.0. Provided they are backwards-compatible, we can add new features in 8.1 and 8.2.
After recently taking over maintainer-ship of the core contact module, @tim-e and I, in consultation with @andypost and @berdir have formulated a draft roadmap for the features we'd like to see in contact module in the future.
We're publishing it here for wider community-input.

Read more
David_Rothstein's picture

Drupal core security release window on Wednesday, July 16

Start: 
2014-07-16 (All day) America/New_York
Organizers: 

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

Read more
mparker17's picture

Drupal core updates for July 10, 2014

What's new with Drupal 8?

The past two weeks have seen steady progress on Drupal 8, with the release of drupal 8.0-alpha13, the Clearing of the RTBC Queue, the expected deployment of Semantic Versioning support on Drupal.org, the launch of the #D8CX initiative, and the announcement about the roadmap for Drupal Commerce for Drupal 8!

Updates to api.drupal.org

If you go to https://api.drupal.org/api/drupal/8 you'll notice a few updates:

  • A few months ago, we updated the landing page with a list of topics, which were mostly just stubs. Documentation has now been written for most of the topics that are linked from the landing page.
  • There's a list of Services on the right sidebar, which you can filter by tag and name keywords — and each service has its own page, with appropriate cross-linking (list of code that uses the service on the service page, and if a service name is used in code, it should link to the service page)
  • The Classes page now lists Traits as well as classes and interfaces
  • For hooks like hook_form_FORM_ID_alter(), you can now see a list of functions that implement it (previously this only worked for hooks like hook_form_alter() where the function name was modulename_hookname(), but now it works for ALL_CAPS replacements as well).

Where's Drupal 8 at in terms of release?

Last week, we fixed 1 critical issue and 5 major issues, and opened 2 criticals and 10 majors. That puts us overall at 97 release-blocking critical issues and 614 major 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, we could use your help!

More ways to help

Issue #1679344: Race condition in node_save() when not using DB for cache_field recently caused a Drupal.org outage. The issue already has a proposed resolution recommended in comment #24 — help out by creating a patch for either D7 or D8.

Additionally, there are a bunch of easy documentation issues which need some help moving forward. For each of these, there is a "Child Issues" sidebar. Look there for issues that are "active", "needs work", or "needs review":

If you want to get started with the core development process, this is a great way to get your first commit in core!

You can also search the Drupal Core issue queue for issues tagged "Novice": the ones in the "documentation" component are especially good for new contributors.

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.

You can also help by sponsoring Drupal core development.

Read more
Gábor Hojtsy's picture

Drupal 8 core sprints, August 7-10

Start: 
2014-08-07 (All day) - 2014-08-10 (All day) UTC

Summer is in full swing, but we know you enjoy Drupaling with your peers in the summer as much as any other time of the year! Plus, this summer is an important time to help get Drupal 8 done, so there is no good reason to skip getting together. We are holding two Drupal 8 sprints at the same time on August 7 to 10: one in North America at TCDrupal, and one in Europe at Drupalaton. Sprinters from both events will collaborate on Drupal 8 issues.

Twin Cities DrupalCamp (North America)

Twin Cities DrupalCamp hosts a four-day Drupal sprint, with a focus on unblocking the release of Drupal 8 and other topics like multilingual, accessibility, and Drupal.org. The last day of the event provides a mentored sprint which is ideal for Drupalers new to sprinting or the issue queues. The camp itself features keynotes from Holly Ross and Chris Shattuck, free Drupal training on the first day, and five parallel session tracks on the middle days. The event is in Minneapolis and Bloomington, MN and the early bird ticket is $35. If you need funding to attend, contact the organizers.

Drupalaton (Europe)

Great location for a summer camp in an affordable hotel right on the beach of the biggest warm water lake in Europe (with a tiny private island), Drupalaton sprints provide a relaxed environment to work and have fun together. The camp programme focuses on providing longer hands-on workshops with featured speakers Ruben Teijeiro, Campbell Vertesi, Adam Juran and Gábor Hojtsy. The event is in Keszthely, Hungary and the ticket is 50 EUR. There is a funding pool for sprinters who would not attend otherwise; contact the organizers.

P.S. Even if you cannot attend in August, keep in mind we have 9 consecutive days of sprints coming up in September in Amsterdam around DrupalCon.

Read more
tvn's picture

Drupal.org User Interviews: looking for core developers

Hi all,

I am looking for a few core developers, willing to take part in 45-60 minute user interviews next week. These interviews are part of the User Research we are doing now, they will help inform the future Drupal.org redesign.

If you have time and desire to talk to us about Drupal.org, let me know!

Thanks.

jhodgdon's picture

This Month in Drupal Documentation - June 2014

Welcome to the second This Month in Drupal Documentation!

"This Month in Drupal Documentation" (TMIDD) is an approximately monthly update from the Documentation Working Group (DocWG) on what has been happening in Drupal Documentation in the last month or so. Sorry... because this is posted in the Core group as well as Documentation, comments are disabled.

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

Read more
David_Rothstein's picture

No Drupal 6 or Drupal 7 core release on Wednesday, July 2

The monthly Drupal core bug fix release window is scheduled for this Wednesday. However, the last release was two months ago, and there haven't been enough changes to the development version since then to warrant a new release.

(Note that there will be a Drupal 8 alpha release on July 2, but Drupal 8 is still under development and therefore on a different schedule than the stable core releases.)

Read more
catch's picture

Drupal 8 alpha 13 on July 2nd

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

June 30th-July 1st, 2014 Only critical and major patches committed
July 2nd, 2014 Drupal 8.0-alpha13 released. Emergency commits only.
July 3rd-5th, 2014 Disruptive patch window
larowlan's picture

Booting D8CX

Background

Now that we're nearly down to single figures for beta-blockers a few of us have started organizing around a D8CX initiative similar to that run during the Drupal 6->7 update. Talk on irc over a month-or-so led to a formal kick-off meeting to set down some goals and get some action items.

What is D8CX I hear you say

Back in the Drupal 6 -> Drupal 7 cycle the D7CX initiative promoted/assisted contrib modules porting from Drupal 6 to 7.

Read more
xjm's picture

This month in Drupal Core (June 25, 2014)

Note: We've renamed this post series to Drupal Core Updates since, well, you know, they weren't exactly weekly to begin with. (As always, contact xjm if you'd like to help write them!)

What's new with Drupal 8?

We may have been quiet for the past month as we prepared for -- and then recovered from -- DrupalCon Austin, but core development has been sizzling! (And not just because of the Texas climate.)


Photo credit: pdjohnson

DrupalCon Austin sprints

In addition to all the great sessions (videos below), summits, BOFs, and trainings, Austin included six full days of sprints on everything from Drupal 8 release blockers, frontend, and APIs, to D8 contrib initiatives like #d8rules, the Examples D8 port, and D8 Media, to Drupal.org itself. Nearly 500 sprinters and mentors got involved on the main Friday sprint day, and over 100 sprinters participated in the extended sprints before and after the Con.

If you were at the sprints, you might have noticed a few goofy sprinters decked in rabbit ears. :) These indefatigable contributors were working on some of the very last Drupal 8 beta blockers. During Austin, we managed to resolve six of these issues, but more importantly, we identified the path forward in all the beta blockers we didn't fix as well.

Done > Perfect

The past month also showed a shift in the community's outlook: It's time to get Drupal 8 done. We need to stop making large, non-essential changes, because every time we make more work for ourselves, we delay the release of 8.0.0 for hundreds of thousands of people. When we have a choice between doing something quickly and imperfectly, or slowly and perfectly, it's time to pick the quick, imperfect fix. A couple examples:

  • Last month, we discovered that Drupal 8's new support for PHP INTL dates was badly broken. Instead of spending dozens of hours trying to resolve this issue before releasing a beta, we removed the feature. It did not exist in D7, and it can be added back for 8.1.0, or provided by a contributed module.
  • In Drupal 8, comment fields can now be attached to any entity type, instead of just nodes; however, they don't work on entity types with non-numeric ID keys (contact forms are the only example in Drupal 8 core). Instead of holding up the release on making every fieldable entity type commentable, we settled for almost every entity type being commentable -- which is still a big improvement from D7.

Drupal 8.0.0 will not be perfect, but it will be powerful. And we have the chance to make it even better in 8.1.0 six months later. Think about which issues in the core queue might make sense as minor version targets, and help us work on Drupal 8 efficiently.


Photo credit: Michael Schmid. Help us battle Lord Over-Engineering!

Drupal 8 documentation updates on API.drupal.org

Lots of comprehensive API documentation has been added to the API.Drupal.org handbook page over the past month, thanks especially to API documentation maintainer jhodgdon and review efforts from core component maintainers. This overview page (and the detailed documentation linked from it) should provide a much better starting point for learning about Drupal 8. (See below for how you can help document the remaining API topics.) API.drupal.org has also recently added an automatic list of services provided in Drupal 8 core. For updates on Drupal documentation work, see This Month in Drupal Documentation.

Where's Drupal 8 at in terms of release?

Last week, we fixed 9 critical issues and 10 major issues, and opened 4 criticals and 6 majors. That puts us overall at 92 release-blocking critical issues and 595 major issues.

2 beta-blocking issues were fixed last week. There are still 11 of 172 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.

  • #2238217: [Change record] Introduce a RouteMatch class

    The one reasonably approachable task in this week's top beta blockers is to complete the needed change record documentation for the recently added RouteMatch class. Help by writing a draft change record for the issue, and then update existing change records to also include an issue reference to #2238217 and to use the new API. (See comment #143 on the issue for a start.) Post links to the revision diffs for your change record updates so they can be reviewed by other contributors.

  • #2256521: New plan, Phase 2: Implement menu links as plugins, including static admin links and views, and custom links with menu_link_content entity, all managed via menu_ui module

    This massive (nearly 600 K) improvement to the Drupal 8 menu link API resolves or unblocks numerous critical issues while also supporting performance, DX, and multilingual improvements. The patch is developed from a sandbox:
    git clone --branch 2256521 http://git.drupal.org/sandbox/dereine/2031809.git
    Help this issue by:

    • Providing code additional reviews, since the patch is way too big for any one contributor to review in one sitting.
    • Proactively identifying things in the patch (or from others' reviews) that could be resolved in followup issues, filing those followup issues, and adding the appropriate code @todo and links to the followup issues.
    • Looking through the patch and issue to identify the complete, specific API changes it introduces, and adding these changes to the issue summary.
    • Checking for existing change records that will need to be updated for these API changes, listing the updates that will be needed in the issue summary, and editing the change records to add a reference to #2256521.
    • Drafting a new change record for the change.

    Check with Wim Leers, pwolanin, or dawehner so that you can align your efforts with their work on this patch.

  • #2144263: Decouple entity field storage from configurable fields

    This issue is key to completing the Drupal 8 Entity Field API and is the culmination of work done across DrupalCons Portland, Prague, and Austin. The patch needs test failures resolved, architectural review, and (as above) identification of any needed change record updates. Coordinate with Berdir, plach, or yched to help further with this issue.

  • #1825952: Turn on twig autoescape by default.

    Enabling Twig's built-in autoescaping of HTML-unsafe code will security-harden Drupal 8, and should eventually allow us to reduce complexity and improve perfomance in the theme layer. The patch introduces a SafeMarkup class that can be used to identify sanitized strings for use in templates, and all other strings are automatically escaped. Help with this patch by providing feedback to points raised in recent reviews (see comment #185), helping write thorough API documentation for the SafeMarkup class, or starting a draft change record. Contact xjm to help out with this issue.


Photo credit: Michael Schmid

More ways to help

  • We're closing in on Beta 1!

    Only 11 beta-blocking issues remain, and we will probably be in the single digits by the end of the week. This means now is a good time to start looking at all the beta targets and especially issues with a beta deadline. (See Beta blocker deadline target what? for an explanation of these issue categories.) Keep an eye out for other issues that should have a beta deadline as well.

  • #2148255: [meta] Make better D8 api.d.o landing page, linked to high-level overview topics, and put it in Core api.php files

    Help improve our Drupal 8 API documentation! The menu and routing topic needs review, and we also need first drafts for the REST, Migration, and Ajax documentation topic updates.

  • #1971384: [META] Convert page callbacks to controllers

    We converted all of core to use our new routing system last fall, but eighteen different form and page controllers still need to be cleaned up to conform to our best practices. Currently, almost all of these patches need to be rerolled for PSR-4 and for other core changes. Note, however, that many of these patches have gone through multiple rerolls (mostly by novice contributors) over the course of more than a year, without sufficient review before the patches become stale. So, what these issues need most is 1-2 experienced contributors with an understanding of Drupal 8 architectural concepts who can manage the meta issue and its children, and provide thorough code review when new patches are submitted. If you can help out, start by reviewing those child issues still at "Needs review".

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

    Drupal 8 core provides numerous entity types, but the full public API for each type is not easily documented or discoverable. To improve the developer experience, each entity type interface is being expanded with relevant methods for the specific entity. Most issues have a submitted patch, and what is most needed is architectural review of the proposed interface methods, including recommending which properties should instead be protected. 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.

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.

You can also help by sponsoring Drupal core development.

Read more
pwolanin's picture

Core Sprint: Drupal 8 at the Jersey Shore

Start: 
2014-07-12 09:00 - 2014-07-13 17:00 America/New_York

Join members of the NJ Drupal Community at our upcoming sprint: Drupal 8 at the Jersey Shore. The event will be held in Asbury Park, NJ and run all day on Saturday, July 12 and Sunday, July 13.

Join like-minded Drupal contributors for two full days of core and contrib sprinting to further advance Drupal 8. We'll have a list of approachable Drupal 8 critical tasks for participants to work on (thanks to remote help from xjm).

Read more
David_Rothstein's picture

Drupal core security release window on Wednesday, June 18

Start: 
2014-06-18 (All day) America/New_York
Organizers: 

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

Read more
Gábor Hojtsy's picture

All the sprints at and around DrupalCon Amsterdam

Start: 
2014-09-27 09:00 - 2014-10-05 23:55 Europe/Amsterdam

We have a great tradition of extended sprints around big Drupal events including DrupalCons and Drupal Dev Days. 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 Amsterdam 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 space, internet, coffee, tea and maybe food. There are already various sprints signed up including Multilingual, Drupal.org, Rules, Media, Content staging, Migration and Frontend. We are really friendly and need all kinds of expertise!

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

Read more
David_Rothstein's picture

No Drupal core release on Wednesday, June 4

The monthly Drupal core bug fix release window is scheduled for this Wednesday. However, the last release was a month ago and this is DrupalCon week, so there won't be a bug fix release this month. Enjoy DrupalCon (those of you who are there)!

Upcoming release windows include:

  • Wednesday, June 18 (security release window)
  • Wednesday, July 2 (bug fix release window)
Read more
jhodgdon's picture

This Month in Drupal Documentation

Introducing... This Month in Drupal Documentation (TMIDD)

Similar to "This Week in Drupal Core", the relatively new Documentation Working Group (DocWG) is trying out a new communication strategy: an approximately monthly post on what is happening in Drupal Documentation. We'll be posting this both to the Core and Documentation groups on groups.drupal.org, and because it is posted to Core, comments will be disabled by policy.

Read more
xjm's picture

Rerolling patches for PSR-4

All Drupal 8 core module code was recently converted to the PSR-4 standard. This issue moved hundreds of files and so many patches will need rerolls. You can update patches safely with the following workflow (provided by @donquixote):

Read more
xjm's picture

Beta blocker deadline target what? A quick guide to Drupal 8 release management tags

Drupal 8's feature freeze was over a year ago, and we are close to releasing a Drupal 8 beta to provide testers and contributed module authors with what they need to prepare for Drupal 8.0. What does this mean for issues in the core queue? When we look at Drupal core issues, we should ask two questions:

  1. Is this issue worth holding up the entire Drupal 8 release (no one can use Drupal 8 until it's done)?
  2. If not, what deadline does it have?

Here's a guide to how we organize issues based on the answers to these questions.

Read more
Subscribe with RSS Syndicate content

Core

Group events

Add to calendar

Group notifications

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

Hot content this week