Upgrade Your Drupal Skills

We trained 1,000+ Drupal Developers over the last decade.

See Advanced Courses NAH, I know Enough
Mar 25 2024
Mar 25

Drupal 11 development has reached a point where the system requirements are being raised in the development branch. To prepare core developers for this and to inform the community at large, we are announcing the following requirements for Drupal 11.

Webserver

We announced in mid-February that there is an RFC to remove support for Windows in production. Other webserver requirements are unchanged.

PHP

Drupal 11 will require PHP 8.3 and older versions of PHP are not supported. Note that as of Drupal 9.4, a policy was adopted to automatically drop support for PHP versions no longer supported by the PHP maintainers, so future minor versions of Drupal 11 will increase the requirement further.

Database

The minimum database requirements for backends supported by Drupal 11 are MySQL 8.0, MariaDB 10.6, PostgreSQL 16 and SQLite 3.45.

Composer

Similar to Drupal 10.2, Drupal 11 will require Composer 2.7.0 or newer; this change was made for the Composer security fix released in February 2024.

Browsers

The existing browser policy has not changed and there was no need to update it for Drupal 11. Drupal already drops support for older versions of browsers as new ones get released.

PHP and JavaScript dependencies

Drupal 11 will depend on Symfony 7, PHPUnit 10 and jQuery 4, work is ongoing to update to these versions.

Drupal 10 will receive long term support

Drupal 10 will continue to be supported until mid-late 2026 and the release of Drupal 12.

Mar 07 2024
Mar 07

In November 2023, we announced three possible release windows for Drupal 11 based on when beta requirements will be completed. We opened the development branch two weeks ago.

Major version updates of dependencies in Drupal 11 include Symfony 7, jQuery 4 and PHPUnit 10 or 11. Based on our findings with the PHPUnit 10 update particularly, we already see that the first release window in June will not be possible for Drupal 11.

The two remaining potential release windows for Drupal 11 are as follows:

  • If Drupal 11 beta requirements are done by April 26, 2024: Drupal 11.0.0-beta1 on the week of April 29, 2024. RC1 on the week of July 1, 2024 and stable release on the week of July 29, 2024.
  • If Drupal 11 beta requirements are done later by September 13, 2024: Drupal 11.0.0-beta1 will be on the week of September 16, 2024. RC1 on the week of November 11, 2024 and stable release on the week of December 9, 2024. In this case the same versions of Drupal 10.4 are planned for the same release windows.

 
Drupal 11 release scenarios visualized (as explained in the text)

Help with getting Drupal 11 ready

Most help is needed around the update to PHPUnit 10, while the Symfony 7 update and jQuery 4 update issues also have more work to do. Join the #d11readiness channel on Drupal Slack to discuss issues live with contributors.

Get involved in person

In the earlier scenario, Drupal 11 will be in beta the week before DrupalCon Portland 2024, while in the later scenario it will be in beta the week before DrupalCon Barcelona 2024. We'll be working on outstanding core issues at the time and updating contributed projects as well at those events.

Drupal 10.3 will be released on the week of June 17, 2024

While the release dates of its alpha and beta version may be different based on the scenario, Drupal 10.3.0 is planned to have a release candidate on the week of June 3, 2024 and a release on the week of June 17, 2024, independent of when Drupal 11 is released.

Feb 21 2024
Feb 21

Starting today, the Drupal 11.x branch is used for building the next major Drupal version, Drupal 11. This means that major version specific changes can now happen on the Drupal 11.x branch. This includes dependency and requirements updates and removal of deprecated API and extensions. Details are available in the allowed changes during Drupal core release cycle document.

Drupal 11 is planned to be released either on the week of June 17, week of July 29 or week of December 9, 2024, depending on when beta requirements are completed.

A 10.3.x branch was created to work on the upcoming minor version. Drupal 10.3.0 will be released on the week of June 17, 2024.

Issues should remain targeted at the 11.x branch and will be backported when appropriate.

Feb 12 2024
Feb 12
Onwards to Drupal 11 - ways to get involved | Gábor Hojtsy on Drupal

Breadcrumb

Feb 12 2024
Feb 12
Looking for your input for DrupalCon Portland 2024 initiative highlights | Gábor Hojtsy on Drupal

Breadcrumb

Feb 09 2024
Feb 09
Upgraded my blog from Drupal 7 to Drupal 10 in less than 24 hours with the open source Acquia Migrate Accelerate | Gábor Hojtsy on Drupal

Breadcrumb

Feb 06 2024
Feb 06

To continue automated testing, projects must convert to GitLab CI and contributors must switch from patches to merge requests by July 1, 2024.

As of July 2023, contributed projects are fully equipped to adopt GitLab CI. In October 2023 we announced that Gitlab CI testing of Drupal core was already five times faster than the legacy DrupalCI system. In our December 2023 maintainer email we announced that our legacy DrupalCI will be retired as soon as July 2024. Now we are announcing further details.

What's happening?

The DrupalCi to GitLab Ci transition visualized

Some DrupalCI features are already turned off

Projects without DrupalCI testing configured cannot add it anymore. Direct access to log output and artifacts on DrupalCI is no longer available. Results are still summarized on the Automated Testing tab of those project's pages.

With the exception of Drupal 7, it is not possible to run tests on patches against Drupal core anymore. Even for Drupal 7, patches need to be sent for testing manually.

Changing DrupalCI schedules ends on April 30, 2024

After April 30, 2024, DrupalCI schedules can not be added or changed, except to remove DrupalCI testing. Tests will keep running with existing configured schedules until removed.

DrupalCI and all patch testing will be turned off on July 1, 2024

No DrupalCI tests will be executed after this date. It will also no longer be possible to run tests on any patches on Drupal.org on any project. Existing test results will be kept for six months.

All results from DrupalCI tests will be removed on January 1, 2025

This is the end of DrupalCI data retention. No testing results will be available beyond January 1, 2025.

What to do about it?

Most projects can start GitLab CI testing with a provided template .gitlab-ci.yml

Using GitLab CI for testing may seem intimidating at first but the Drupal Association engineering team and a number of community volunteers have spent a lot of time to make it as easy as possible for you to adopt GitLab CI for testing.

There is a preconfigured .gitlab-ci.yml template that will set up everything you need to test your project. This template has several useful features, including a variables file that will be automatically updated by the Drupal Association, to make sure you’re always testing against the currently supported versions of Drupal.

Most project maintainers won’t have to make any changes to the template, just commit the template to your project and your testing should work right away!

Set up GitLab CI for your drupal.org project today.

Contributors must use merge requests on all projects to get automated testing after July 1, 2024

GitLab CI, like almost all modern CI systems, is designed to test merge requests. If you have ever contributed to a project on GitHub, you pretty much already know how it works. The advantage of Drupal.org merge requests is that they are collaborative by default, so you and fellow contributors can work in the same fork.

Read the best practices for contributing through merge requests.

Dec 15 2023
Dec 15

New in Drupal 10.2

The second feature release of Drupal 10 improves content modeling, block management, menu and taxonomy organization, and permission administration. New options to sanitize file names make it possible to clean up the names of uploaded files, and media item revisions now have a dedicated user interface.

Easier content management

10.2 improves the user experience for managing several types of content:

  • Field types for new fields are visually listed instead of a simple select list. Settings for fields are now all included on one form.
  • Menu items and taxonomy terms have a dedicated option to add a child item, which makes item placement easier.
  • Media items now have a dedicated user interface to review and manage older revisions.
  • CKEditor's language selector can now be configured to only show languages supported on the site.

More flexible block placement

A user interface has been added to show or hide each block based on the HTTP response status, so that specific blocks can be added or removed when the page is not found (404) or access is denied (403).

New built-in file name sanitization options

The functionality of one of the most popular contributed modules is now included in core! Replace whitespace in file names, transliterate text, convert to lowercase, and more.

Faster permission management

The permissions page now comes with a filter on the top to make it easy to find the permission you planned to adjust.

Performance improvements

Drupal 10.2 includes numerous performance improvements for content rendering and HTTP responses, as well as improved caching APIs.

Works on the latest PHP

PHP 8.3 was released three weeks ago, and Drupal 10.2 is already compatible with it.

Modern language feature: PHP attributes

Drupal core has started adopting PHP attributes, a modern PHP language feature, to provide better developer experience for plugin annotations. Contributed and custom code can begin adopting this improved API for their plugins, and Block and Action plugins can all be converted to the new API.

Built-in project news updates

To help keep you up to date with project news, the Announcements Feed module became stable and is now installed by default with the standard profile.

Help topics now in Help module

The experimental Help topics module is now marked as deprecated and all functionality has been integrated into the core Help module.

Developer experience improvements

Drupal 10.2 comes with a number of developer experience improvements:

  • A PerformanceTestBase was added to support automated testing of performance metrics with support to send OpenTelemetry traces to an open telemetry endpoint.
  • A new DeprecationHelper::backwardsCompatibleCall() method is available that helps write Drupal extensions that are compatible with multiple major versions at once.
  • PHP Fibers support was added to BigPipe and the Renderer, which allows Drupal to potentially run different code while it's waiting for an asynchronous operation to return.
  • Configuration validation was expanded to better support strict testing and make configuration form validation easier to implement.
  • Symfony's autowiring support was adopted for services, based on PHP 8 attributes, making service creation easier.
  • The HTML utility classes and filter system was updated to produce HTML5 syntax instead of XHTML.

Core team updates

Drupal is built by an open source community of collaborators across geographies and organizations. Maintainers assess the work of the community and decide when it's ready to commit to Drupal core. After a period as a provisional committer, Dave Long (at Full Fat Things) was promoted to a full release manager. Kristiaan Van den Eynde (at Factorial) and Adam Bramley (at PreviousNext) have also become core subsystem maintainers. Thanks for stepping up!

Want to get involved?

If you are looking to make the leap from Drupal user to Drupal contributor, or you want to share resources with your team as part of their professional development, there are many opportunities to deepen your Drupal skill set and give back to the community. Check out the Drupal contributor guide, or join us at DrupalCon Portland and attend sessions, network, and enjoy mentorship for your first contributions.

Nov 22 2023
Nov 22

New major release schedule

Beginning with Drupal 10, a new Drupal major version will be released every two years in even years (2022, 2024, etc.). Each major version will receive active support for about two years, followed by maintenance support and security coverage for about two more years. Each is supported until two more major versions have been released.

Chart illustrating the overlapping support of Drupal minor and major versions from 2024 to 2027, explained below.
This is an example.
The exact schedule varies, and will be published on the Drupal core release schedule.

Drupal 11 will be released in 2024

Drupal 11 will be released sometime in 2024. Like Drupal 9.0 and 10.0, Drupal 11.0 has three potential release windows, in June, August, and December. The window used will depend on when the beta requirements are complete. For more information, refer to the Drupal core release schedule.

Drupal 11 alpha development opens this week

Following the release of 10.2.0-beta1, changes to 11.x that diverge from Drupal 10 under the continuous upgrade path will begin. Anyone can get involved in completing the requirements for Drupal 11. Join the #d11readiness channel in the Drupal community Slack.

Maintenance minor versions of Drupal 10

Following the release of Drupal 11.0.0 in 2024, a long-term support phase for Drupal 10 begins, and it will include a new maintenance minor every six months. Each maintenance minor will contain a limited set of changes backported from Drupal 11. For more information, refer to the Drupal core release process overview.

Use a supported PHP version for the best ongoing support

Maintenance minor releases for Drupal 10 will keep adding support for newer PHP versions as they are released. The minimum supported PHP version for Drupal core follows the PHP core team's support cycle. (Reference: What does it mean for a PHP version to be supported?)

Site owners wishing to take advantage of Drupal 10's long-term support phase should ensure their platforms always use PHP versions supported by the PHP maintainers.

Announcement written in collaboration by Dave Long, Jess (xjm), Nathaniel Catchpole and Victoria Spagnolo.

May 05 2022
May 05
The epic story of the last week of how Drupal's frontend and backend look changed after 11 years at DrupalCon Portland | Gábor Hojtsy on Drupal

Breadcrumb

Apr 13 2022
Apr 13
Gather interest and involve contributors for your projects at Drupal events | Gábor Hojtsy on Drupal

Breadcrumb

Jan 27 2022
Jan 27
Drupal 9 and Drupal 10 readiness at Drupal Global Contribution Weekend 2022 | Gábor Hojtsy on Drupal

Breadcrumb

Dec 22 2021
Dec 22
Major Drupal configuration schema cheat sheet update - 7 years later | Gábor Hojtsy on Drupal

Breadcrumb

Nov 29 2021
Nov 29
The big Symfony 4 to 6 jump plan in Drupal 10 and potential benefits down the line for future versions | Gábor Hojtsy on Drupal

Breadcrumb

Nov 02 2021
Nov 02
Drupal 8 is end of life today: the compendium | Gábor Hojtsy on Drupal

Breadcrumb

Nov 01 2021
Nov 01
One day to go until Drupal 8 EOL: what if you stay on Drupal 8? | Gábor Hojtsy on Drupal

Breadcrumb

Oct 31 2021
Oct 31
Two days to go until Drupal 8 EOL: looking ahead to future versions | Gábor Hojtsy on Drupal

Breadcrumb

Oct 30 2021
Oct 30
Three days to go until Drupal 8 EOL: you may already be using an EOL version of Drupal 8 | Gábor Hojtsy on Drupal

Breadcrumb

Oct 29 2021
Oct 29
Four days to go until Drupal 8 EOL: use Drupal 9 on older MySQL/Percona/MariaDB versions | Gábor Hojtsy on Drupal

Breadcrumb

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web