'Stable Release Request' Issue Template

Problem/Motivation

I've been toying with the idea of defining a issue template to help define interest in and give scaffolding for maintainers to adopt/adapt to plan a stable release of their module.

I'd like to facililtate discussion, feedback, changes to this template to develop a template worthy for cross-posting across issues in an effort to help scaffold a plan for a D9-compatible stable release.

Proposed Issue title

Project Name X.0.0 stable release plan

Example

Maintainer Support 1.0.0 stable release plan

Proposed Template

Problem/Motivation

The intent of this issue is to help the maintainer(s) coordinate community efforts in the creation of a stable release. Community involvement is only intended as a suggestion; it is up to maintainers to ultimately decide the creation of, and what goes into, a stable release. If you are not interested in using this issue, please mark the issue as Fixed or Closed (works as designed).

As of the creation of this issue, this project presently does not have a stable release compatible with Drupal 9+. There are many benefits to publishing a stable release for a module. Project Browser → uses stable releases as a recommended criteria for module discovery ( #3240314-16: Decide on algorithm for "recommended" modules → ).

Release-blocker issues

• issues tbd

Good-to-fix issues

• issues tbd

Above and beyond tasks

• Create issue fix list for stable release using the grn tool → .

Remaining tasks

• Establish a list of release-blockers and 'good-to-fix' issues for a stable release.
• Resolve above issues blocking the release of a stable release.
• Craft changelog for new release.
• Create new release.

Do you have resources you'd like to contribute to this template? Have feedback on the stable release request issue template? We want your feedback: #3239062: 'Stable Release Request' Issue Template →

Original issue summary

(optional, the original issue summary)