React can rightfully be called a game-changer JavaScript library for Drupal developers, as it can completely change the way interfaces are built. By integrating it into Drupal themes, we can enter a completely new world full of creativity and convenient functions, thus improving user experiences significantly.
With the help of React, interfaces of websites built on Drupal will no longer be static and boring: they become real, interactive, and fast. Less words, let's learn more details about how you can benefit from using React in Drupal themes.
This week I built a LocalGov Drupal dashboard, so we can better keep track of all our projects.
Whenever a new major version of Drupal is released, we update Drupal's GitLab CI testing templates to automatically update the versions being tested. Here's an outline of our plan:
Drupal 11 was released on August 6th. You can learn more about it on the Drupal 11 landing page.
This means that we are in the middle of a transition period where many sites and modules will want to be in Drupal 11, whereas some others might still want to stay in Drupal 10.
From a GitLab CI point of view, testing for both Drupal 10 and 11 simultaneously has been available for months, providing module maintainers with a great tool to test their code before Drupal 11 was launched.
This was available by setting one variable in the .gitlab-ci.yml like this:
variables:
OPT_IN_TEST_NEXT_MAJOR: 1Many maintainers have leveraged this already and we can see many modules already claiming full Drupal 11 support within days of the release. To be more specific, as of August 20th, 2870 projects have no compatibility errors anymore, and 1720 have made Drupal 11 compatible releases.
We are preparing to update the default testing configuration for the GitLab CI templates, but we want to make sure to continue to support maintainers who still need to test against Drupal 10 and 11. We've outlined the changes we'll be making and the timeline below.
As of today:
When we do the shift, this will change to:
For modules that were testing Drupal 10 and Drupal 11 simultaneously, the change will be as easy as this:
variables:
# OPT_IN_TEST_NEXT_MAJOR: 1
OPT_IN_TEST_PREVIOUS_MAJOR: 1Instead of opting in to test the next major, all you need to do is opt into the previous major.
Note: Drupal 12 development branch does not exist yet. Enabling this version might not do anything until this branch is created.
We are actively working on making the above switch in this issue: Update templates so 11.0 is the default/current branch.
We are going to be taking the following steps in the coming days / weeks.
We will set the default value for OPT_IN_TEST_NEXT_MAJOR to 1 temporarily, and release version 1.5.6 of the templates. This will automatically become the default for all Contrib.
Modules that have not yet tested their code against Drupal 11 will now see "Next Major" test jobs in their pipelines, in addition to the "current" Drupal 10 variant. These new jobs have allow_failure: true, so the overall result of the pipelines should not change. This should show a good sense of where the module is at in relation to Drupal 11. Maintainers can still override the variable to be 0 if they don't want this behavior.
The expected date for this change is: August 26th, 2024 (next Monday)
When the issue Update templates so 11.0 is the default/current branch and all its dependencies all sorted, we will deploy the changes and create a new release 1.6.0. This will be available to Contrib projects using "gitlab ref" main or 1.x-latest
The expected date for this change is: September 5th, 2024 (2 weeks from now)
Then we will make this new release be the default for all contrib projects automatically.
However, we have provided several alternatives for modules that don't want to do the shift at this point. Any of the following can be used:
OPT_IN_TEST_PREVIOUS_MAJOR to 1 and OPT_IN_TEST_CURRENT to 0 to continue testing Drupal 10 and not Drupal 11.For those wanting to do the shift, you will not need to do anything at all.
The expected date for this change is: September 12th, 2024 (3 weeks from now)
Onwards and upwards, that means that Drupal 11 is the default version to be tested for all new issues, merge requests, and pipelines for all contrib projects, allowing us to keep the Drupal ecosystem up to date and relevant.
There are some issues that are not blockers for this change, but are related, so we encourage you to see the issue list before reporting anything new, but otherwise create a new issue if you discover a problem and don't find it in the queue.
We talk with Janez Urevc from Tag1 Consulting about Gander, an open-source automated performance testing framework.
Professional module development - 15 weeks, 90 hours, live, online course.
Drupal Career Online - 12 weeks, 77 hours, live online, beginner-focused course.
We're using the machine-driven Amazon Transcribe service to provide an audio transcript of this episode.
Subscribe to our podcast on iTunes, iHeart, Amazon, YouTube, or Spotify.
If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or corrections. If you'd rather just send us an email, please use our contact page.
Podcast edited by Amelia Anello.
PORTLAND, Ore., 22 August 2024—The Drupal Association is pleased to announce Tag1 Consulting as a partner for the Drupal 7 Extended Security Support Provider Program. This initiative aims to support Drupal 7 users by carefully selecting providers to deliver extended security support services beyond the 5 January 2025 end-of-life (EOL) date.
The Drupal 7 Extended Security Support Provider Program allows organizations that cannot migrate from Drupal 7 to newer versions by the EOL date to continue using a version of Drupal 7 that is secure and compliant. This program complements the Association’s Drupal 7 Certified Migration Providers Program, which Tag1 is also a participant in, that helps organizations find the right partner to transition their sites from Drupal 7 to Drupal 11.
Tag1’s Drupal 7 extended support offers proactive security and compatibility updates for D7, backed by their team of top Drupal contributors and security experts who led its creation and evolution. With their support, users can continue running D7 as long as they need.
“We’re very pleased to add Tag1 to our Drupal 7 Extended Security Support Program,” commented Tim Doyle, CEO of the Drupal Association. “Tag1 brings a wealth of experience with Drupal and the Drupal Community, and we’re happy they’re applying their expertise to Drupal 7 support.”
As organizations prepare for the transition from Drupal 7, Tag1 Consulting will provide the necessary support to keep their sites secure and operational.
“As one of the oldest and most well-known consulting companies in the Drupal ecosystem, we're proud to offer trusted support for Drupal 7 after its end of life,” said Jeremy Andrews, Tag1’s CEO. “Our team is dedicated to helping organizations keep their sites secure and running smoothly, with the same expertise and care that we've brought to the community for over 20 years.”
More information on Drupal 7 Extended Support from Tag1.
The Drupal Association is a nonprofit organization that fosters and supports the Drupal software project, the community, and its growth. Our mission is to drive innovation and adoption of Drupal as a high-impact digital public good, hand-in-hand with our open source community. Through various initiatives, events, and programs, the Drupal Association helps ensure the ongoing development and success of the Drupal project.
Tag1 is a global technology consulting firm and recognized leader in the Drupal community. Known for our innovative work with top-tier organizations and our pivotal contributions to the Drupal platform itself, we provide unmatched expertise in key areas such as Drupal architecture, performance, scalability, and security. With over 100 team members across 20+ countries, we are the only organization with experience providing Extended Support for Drupal after End-of-Life, proudly having provided commercial support for Drupal 6 for over six years beyond its EOL. The largest and most well known users of Drupal, with the most demanding security needs have relied on Tag1’s Extended Support including Acquia, Pantheon, Fortive, Symantec, Capegmini, the Drupal Association and Drupal.org.
Worried about the future of your Drupal 7 website? With Drupal 7 reaching end-of-life in January 2025, many site owners and developers are facing a tough decision: migrate to a new version of Drupal or to a new platform altogether, or risk running an unsupported site.
Read more michaelemeyers Thu, 08/22/2024 - 07:00