Summary of the LTS Program

Drupal 6 Long Term Support is a way to continue receiving security and maintenance updates for Drupal Core and contributed projects now that Drupal 6 has reached end of life on Drupal.org

Drupal 6 is no longer supported as of Feb 24th, 2016. The Security Team asked companies who wanted to provide long term support for Drupal 6 and met some qualifications to apply to become the Drupal 6 Long Term Support team. After reviewing many applications we are pleased to announce the following vendors will be providing long term support, with support from the Security team.

These vendors have agreed that in exchange for getting that information they must release all of their patches publicly at the D6LTS project page. This D6 LTS security program does not prevent other vendors from providing support for Drupal 6, including support related to security. These D6 LTS vendors are bound by the same Disclosure Policy as the rest of the team and their clients will not get advanced notice of security issues.

Drupal 6 Long Term Service Vendors

If you plan to run a Drupal 6 site after the end of life date, we encourage you to engage one of the below companies to help pay for their work writing security patches. If they do not have clients paying for their work they will likely stop providing it. News about the addition or withdrawal of support for contributed or core code will be made via the D6LTS project page.


Tag1 Consulting provides expertise in open source software to address performance, scalability, and security challenges. As an official provider of Drupal 6 Long Term Support with a decade of Drupal performance expertise, Tag1 developed Quo (https://quo.tag1consulting.com), a low-cost, hosted monitoring, and security solution for Drupal. With an interactive dashboard, push notifications, and expert support standing by, Tag1 Quo ensures your websites are secure and up-to-date with patches and updates for Drupal core, contributed modules, and themes (all backported and tested by Tag1).


No security team member that worked for any of the above companies was involved in approving or denying other companies.

Usage

Patches for core and contrib are stored in the project's code repository and require developmental skills with knowledge of version control software to use. Rather than handling this yourself, you can hire one of the vendors listed above.

Core patches are rolled against Drupal core 6.38.

Patches for contrib modules and themes are rolled against the latest developmental branch for each.

Note that while some patches may be applied directly to projects and released, most patches are not and these patches need to be manually applied yourself.

See the Version control tab for more details on how to checkout and use Git to access these patches.

Project information

  • caution Maintenance fixes only
    Considered feature-complete by its maintainers.
  • Created by mlhess on , updated
  • shieldStable releases for this project are covered by the security advisory policy.
    There are currently no supported stable releases.

Releases