Consider keeping and fixing a Drupal 7 version

Created on 1 May 2025, 16 days ago

Problem/Motivation

While I understand that Drupal 7 security and bugfix support ended in January, and can appreciate that it is justifiable that the D7 version should stop being maintained.

I would suggest that this is one of several "special" modules for those still on D7 for whatever reason, but might be considering moving to D8+.

Personally, one of my first steps in beginning a migration is to survey the existing site, so modules like upgrade status and hacked are vital and used heavily in that evaluation.

I would have liked to have seen the various issues recently closed productively resolved, rather than having just been closed with the outdated tag.

Many had patches that needed review, often those patches had already had one review, and there seemed to be a reluctance to move the issue to RTBC until a second review had been provided. So it seems a shame that these at least weren't completed.

Given the usage statistic of the 7.x branches of the module, it seems like there are many people potentially considering an upgrade and may now be struggling with patched versions to provide the functionality needed to migrate.
https://www.drupal.org/project/usage/hacked

Proposed resolution

Re-open the D7 issues (or at least those that have solutions offered) and solve the issues by merging a patch or MR to produce a solid final version of the module.
Stop maintenance of the D7 branch, but keep a stable version available for those who may be stuck on D7 for the moment.

Remaining tasks

Reopen tickets
Review any patches offered
Merge patches and MRs
Create a final release
Announce the cessation of maintenance of the D7 branch with a version still available.

Feature request
Status

Active

Version

2.0

Component

Code

Created by

🇬🇧United Kingdom the_g_bomb

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024