Problem/Motivation

Maintaining multiple major versions of a module simultaneously is difficult and time-consuming. Supporting both 8.x-1.x and newer 2.x versions complicates development, testing, and security maintenance. To streamline development and ensure a focused support strategy, we propose dropping support for the 8.x-1.x version. Users are encouraged to upgrade to the 2.0.x version, or the upcoming 2.1.x release when it becomes available.

This approach allows us to concentrate efforts on maintaining a single active version, ensuring regular security releases, bug fixes, and new features for the supported branch while keeping older versions available but without ongoing maintenance.

Steps to reproduce

N/A

Proposed resolution

- Officially drop active support for the 8.x-1.x version, meaning no further security releases, bug fixes, or new features will be provided for this version.
- Update documentation and release notes to inform users about the discontinuation of support for 8.x-1.x.
- Provide clear guidance on upgrading from 8.x-1.x to 2.0.x (and future 2.1.x) versions, including any potential pitfalls or important changes they need to be aware of during the transition.
- Encourage the community to migrate their installations to the latest supported 2.x branch to take advantage of ongoing improvements and security updates.

Remaining tasks

- Draft documentation for the upgrade path from 8.x-1.x to 2.0.x/2.1.x.
- Finalize documentation for the upgrade path from 8.x-1.x to 2.0.x/2.1.x.
- Announce the change to users via appropriate channels (forum posts, release notes, etc.).
- Update module landing pages and repositories to reflect the drop in active support for 8.x-1.x.
- Monitor and address any issues raised by users during the transition period.

User interface changes

N/A

API changes

N/A

Data model changes

N/A

Comments

trackleft2 created an issue. See original summary.

trackleft2’s picture

Issue summary: View changes
greggles’s picture

This seems like a very thorough plan.

There are no bugs reported against the 2.0.x branch, so that's a good sign.

Currently, the usage of the module is:

Week	7.x-1.x	8.x-1.x	2.0.x	Total
December 28, 2024	362	673	789	1,824

As long as the upgrade path works well I think this is a great idea.

trackleft2’s picture

Issue summary: View changes
trackleft2’s picture

Issue summary: View changes
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.