[LarsLaskowski]

Pull Request

📖 Description

Adds a release plan to docs/CONTRIBUTING.md for the releases after 1.3.7. The 65 open issues are grouped into nine GitHub milestones (M1–M9), and each milestone is one release: four patch releases (1.3.8 to 1.3.11) for security, resilience, image identity and update-detection correctness, followed by minor releases 1.4.0 to 1.8.0 for catalog control, data integrity, Portainer actions and notifications. The plan states the dependency chain for the Portainer actions (#273, #279, #276 and #291 before #280) and that #4 and #9 close together with #284 and #293. Documentation only; no code changes.

🎫 Issues

Covers the milestone assignment of #3, #4, #6, #9, #10, #14, #15, #19, #21, #22, #24, #25, #27, #28, #34, #36, #37, #39, #40, #80–#83, #84, #86, #87, #171, #220–#225 and #264–#295.

💬 Reviewer Notes

Please check the grouping and the release order in the new table. The milestones already exist in the repository; no tags or GitHub Releases have been created.

📑 Test Plan

Not applicable, documentation only.

✅ Checklist

• I have added or updated Unit Tests for the change. (n/a, docs only)
• I have read the CONTRIBUTING documentation and followed the project's code style guidelines.

⏭ Next Steps

Work the milestones in order, starting with M1 (v1.3.8).

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud