Transition the project to semantic versioning

Created on 6 October 2023, over 1 year ago

Updated 7 October 2023, over 1 year ago

Problem/Motivation

Comment Notify uses the outdated versioning approach of 8.x-1.x. The new semantic version naming convention is a widely held approach in the open-source community and makes it easier for composer package management.

Proposed resolution

Issues a new release of Comment Notify - 2.0 to follow semantic versioning per these instructions https://www.drupal.org/node/1015226#semver-transition →

Remaining tasks

❌ Get maintainer approval of this plan
❌ Decide what will go in the 2.0 release (See 🌱 Roadmap Active )
❌ Issue 2.0 release

🌱 Plan

Status

Active

Version

1.0

Component

Code

Created by

🇺🇸United States cedewey Denver, CO

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @cedewey
Comment over 1 year ago →
🇺🇸United States greggles Denver, Colorado, USA
This seems like a superb idea to me. I think it could make sense to create a 2.0.0 release that is a pair with one of the 8.x-1.x releases and encourage people to switch, clearly noting on the project page that they are equivalent and that 8.x will be unsupported in a reasonable period of time (e.g. 3-6 months).

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024