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.

David_Rothstein's picture

Drupal core security release window on Wednesday, September 17

Start: 
2014-09-17 (All day) America/New_York
Organizers: 

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

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, October 1.

Read more
Gábor Hojtsy's picture

Drupal core updates for September 4, 2014

What's new with Drupal 8?

It has been a month since the last update on Drupal core development. In the meantime we met and worked hard together at TCDrupal and Drupalaton at the start of August triaging outstanding critical issues and resolving some. Also we collaborated on making Drupal's frontend better at Frontend United at the end of the month.

We've been doing such a great job taking care of the beta blocker issues that we are currently down to only one beta blocker as of this writing. What does this mean? Once we are down to no beta blockers left, a final alpha release is published. If there are no more beta blockers identified during a two-week window, the first beta release is published. Then we'll focus on resolving the hundred or so remaining critical issues to get to release candidates (once all of them are resolved).

Right now, help with the remaining beta blocker as well beta deadline and beta target issues is most welcome. Beta target issues may get in anytime later, but beta deadlines may not unless re-evaluated for inclusion regardless.

The best opportunity to get to work with Drupal developers in person is the 9 (nine) days of sprint opportunities coming up at the end of September at and around DrupalCon Amsterdam. It is the best way to learn Drupal 8 hands-on and help on the way.

Where's Drupal 8 at in terms of release?

Last week, we fixed 8 critical issues and 12 major issues, and opened 4 criticals and 7 majors. That puts us overall at 104 release-blocking critical issues and 644 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

  • Pick a critical issue or beta deadline issue, take the time to thoroughly read the issue (including doing some background reading if necessary to understand the problem space), and then update the issue summary for the issue. Include a summary of the current status and remaining tasks for the issue, and identify any API changes the issue would introduce. Consider whether the change would require a change record or updates to existing change records. Consider what the implications of not resolving the issue would be, or of resolving it after the first beta or after release.
  • We also need help writing help text for core modules like Field UI, Image, Taxonomy and Toolbar. This is an easy way to learn the Drupal Core contribution process and start contributing to Drupal Core.

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 individual Drupal core development.

Read more
David_Rothstein's picture

No Drupal 6 or Drupal 7 core release on Wednesday, September 3

The monthly Drupal core bug fix release window is scheduled for this Wednesday. However, there have been three releases (security releases as well as bug fix releases) in the last month and a half, and not as many changes have been committed to the development version since then as would normally warrant yet another new release.

A Drupal 7 bug fix release during the October release window is likely instead.

Read more
batigolix's picture

This month in Drupal Documentation - August 2014

This is the 'almost' monthly update from the Documentation Working Group (DocWG) on what has been going on in Drupal Documentation. Because this is posted in the Core group, comments for this post are disabled, but if you have comments or suggestions, please see the DocWG home page for how to contact us. Enjoy!

Read more
Gábor Hojtsy's picture

Nine days of hands-on sprinting opportunities at DrupalCon Amsterdam

DrupalCon Amsterdam community sprints are starting in just one month from today. We have a great tradition to organize sprinting opportunities throughout DrupalCon days and also the weekends before and after. If you have been to them, you know the power of these events, but if you are new to our sprints, here are some quotes from an earlier sprint at Drupal Dev Days Szeged:

Two days working with the Drupal Community [...] help you to learn more than one week working alone at home :) -- https://twitter.com/javisr/statuses/449159591373586432

Greatest thing about code sprints: Hearing respected core devs say "I don't understand that." "Me neither." We all learn. [...] -- https://twitter.com/marcvangend/statuses/449442724966858752

Drupal sprints are a wonderful combination of a lot of top Drupal developers working on important problems in the same space without other distractions going on. We even secured a wonderful sprint location for the weekends, the Berlage Workspace. You can help move important issues forward and learn the tricky details faster than anybody else while working with others.


Berlage Workspace street front

Sprints announced so far include frontend, drupal.org, search API, multilingual, Behavior Driven Development, Panopoly, Rules in Drupal 8, Media in Drupal 8, Migration to Drupal 8, Content staging in Drupal 8 and a dedicated group of people driving critical Drupal 8 issues in general. Each team is being lead by Drupal topic experts so you can work with the top people in the field.

The most active days expected in decreasing order are Friday, Monday and Sunday before and Saturday after, but sprinting opportunities are almost always available throughout the nine days. We even created a Google Calendar that you can subscribe to (4j8sqq5fphhpgmrtfl8t2ggkes@group.calendar.google.com) which contains all the sprint venue information at any point in time, so you know where to find active Drupal sprinters. Or just check out the announcement for more information.

The sprints would not happen without the sponsorship of the Drupal Association, Acquia and Open8. Huge thanks for their support!

Read more
xjm's picture

Priority TCDrupalaton sprint tasks!

Today is the start of a double dose of sprint awesome at TCDrupal and Drupalaton. Here are some important sprint tasks to help get Drupal 8 done.

Read more
ifrik's picture

This Month in Drupal Documentation - July 2014

Here's an 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
mparker17's picture

Drupal Core Updates for Aug 4, 2014

What's new with Drupal 8?

It's been an exciting two weeks as Twig Autoescaping was turned on by default, the menu links system was completely revamped, entity caching was finally added to core, and we switched Drupal 8 version numbers to Semantic Versioning!

The switch to semantic versioning means that if you have a clone of Drupal 8 core, you shouldn't patch the 8.x branch anymore: use 8.0.x instead. To switch branches, simply run git fetch origin && git checkout -t origin/8.0.x. See jhodgdon's announcement to the Core group for more information.

The valiant efforts of the 15-person team at the Drupal 8 Code Sprint at the Jersey Shore saw 30 issues move forward, 12 of which have already been committed. For more information, read this recap of the event by Kalpana Goel of Forum One.

Finally, thank you to all the contributors who helped us fix 378 Drupal 8 issues in July, 101 more than in June! The fast turnaround in the RTBC queue from our awesome core maintainers has been really motivating — as of right now the RTBC queue is totally empty, meaning that every RTBC issue has either received committer feedback or been committed. (Also noteworthy, Alex Pott of Chapter Three committed a remarkable 70% of July's many commits. Wow!)

Where's Drupal 8 at in terms of release?

In the past week, we've fixed 9 critical issues and 22 major issues, and opened 4 criticals and 35 majors. That puts us overall at 104 release-blocking critical issues and 656 major issues.

Only 3 of 173 beta blockers remain before we can release a Drupal 8 beta. This means Drupal 8 will soon be in beta, so now is the time to take a close look at the remaining critical issues and beta deadline issues. In each issue, help clarify:

  1. If it's critical or major, why?
  2. What would be the implications of not fixing the issue?
  3. What would be the implications of fixing the issue between betas? (Code changed for modules, upgrade path, etc.)
  4. What would be the implications of fixing the issue after the first release candidate?
  5. What is the next step to make progress? What are the remaining tasks?

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!

  • Issue #1934152: Figure out if we want global config overrides to stick (settings.php overrides don't work on all pages) aims to determine if it would be more secure/sane to apply global configuration overrides hard-coded into settings.php even when they wouldn't normally (for example, when editing/previewing a the configuration of a view in the Views UI, where request/URL don't apply because they're intended for the edit page, not the view itself), or whether it would be better to provide a 2-tiered override system (one for global overrides and one for "soft" request/URL overrides).
  • Issue #2313159: [meta] Make multilingual views work is a collection of problems related to making multi-lingual views in Drupal 8. A number of the sub-issues are "Major", meaning they have significant repercussions but do not render the whole system unusable.

More ways to help

  • Issue #2189661: Replace $form_state['redirect_route'] with setRedirect() aims to make the Form API more consistent with the rest of core, but the patch is out-of-date and needs to be re-rolled.
  • Pick a critical issue or beta deadline issue, take the time to thoroughly read the issue (including doing some background reading if necessary to understand the problem space), and then update the issue summary for the issue. Include a summary of the current status and remaining tasks for the issue, and identify any API changes the issue would introduce. Consider whether the change would require a change record or updates to existing change records. Consider what the implications of not resolving the issue would be, or of resolving it after the first beta or after release.
  • We also need help writing help text for core modules like Entity, Contextual Links, Field UI, Image, Taxonomy and Toolbar. This is an easy way to learn the Drupal Core contribution process and start contributing to Drupal Core.
  • Help brainstorm how to improve core's Contact module for Drupal 8.1 and beyond.

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

Fixing double-escape bugs

Since Twig autoescape is on, there are double escape bugs. If you can fix them by refactoring code into Twig templates, that's great. If not then wait for an easy way to create HTML on the fly without having to create a theme function / template. It's already RTBC, it's a matter of days to find its way in.

Read more
David_Rothstein's picture

Drupal core security release window on Wednesday, August 6 (NOTE: Change from normal schedule)

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

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

Take note of the change in schedule! The security release window is normally the third Wednesday of the month, but we are moving it up for this month only to better coordinate various schedules. Apologies for any inconvenience this change might cause.

Read more
moshe weitzman's picture

Migrate module automated test failures - policy change

The Drupal 8 committers have slightly changed the policy regarding automated test failures as we move toward release of 8.0.0. The traditional policy is that any proposed core patch must pass all automated tests at commit time. We are amending that slightly such that patches which solve Criticals, but fail tests in a non-essential component, are allowed to proceed. For now, the only non-essential component is the Migrate framework.

Read more
jhodgdon's picture

Drupal 8.x is now 8.0.x - new branch

You may have noticed that as of a few days ago that there is a new branch in the Git source code repository for Drupal Core: 8.0.x!

Read more
catch's picture

Drupal 8 alpha 14 on August 6th

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

August 3rd-5th Only critical and major patches committed
August 6th, 2014 Drupal 8.0.0-alpha14 released. Emergency commits only.

(Note that there are two concurrent Drupal 8 sprints Aug. 7-10, so we aren't planning to have the usual "disruptive patch window" following this alpha.)

pwolanin's picture

July 12-13, 2014 Asbury Park, NJ core sprint

On the weekend of July 12-13, 2014 the Central NJ Drupal Group held a core sprint focusing on the upcoming release of Drupal 8. The sprint was attended a great group of Drupal enthusiasts from Chicago, Montreal, New York, Virginia, and of course New Jersey. We took over the Cowerks coworking space in Asbury Park, NJ for the two days and it provided us a fun space to work the day and night away on a variety of issues.

With only seven beta blockers remaining at the time of our sprint, two were on the top of our list of items to work on. Fifteen people participated in person, and the group made progress on two beta blockers (leading to core commits) as well as many other issues.

See the full recap for more details on participants, issues worked on and completed, and a photo gallery.

Read more
David_Rothstein's picture

Drupal 7.30 release this week to fix regressions in the Drupal 7.29 security release

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

The Drupal 7.29 security release contained a security fix to the File module which caused some regressions in Drupal's file handling, particularly for files or images attached to taxonomy terms.

I am planning to release Drupal 7.30 this week to fix as many of these regressions as possible and allow more sites to upgrade past Drupal 7.28. The release could come as early as today (Wednesday July 23).

Read more
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
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: