AI & Machine Learning
Oss Release Policy
Writes an open-source project's release policy as a RELEASES.md contract: the versioning scheme (SemVer, 0.x, CalVer such as YY.N, Go /vN majors, PEP 440, epochs, build numbers), what counts as breaking, pre-release channels, cadence, supported versions and LTS windows, backports, deprecation, and switching schemes safely. Use whenever a maintainer asks SemVer vs CalVer, when to ship 1.0, whether to stay on 0.x, how long to support old versions or whether to offer an LTS - even if they only say minor releases keep breaking users. Not for configuring your own dependency bots or closed-source product lifecycles. Not hosted API versioning - use samber/developer-platform-skills@api-versioning-policy. Not release notes - use samber/developer-relations-skills@changelog-writing.
- Publisher / source
- samber/developer-relations-skills (found on skills.sh)
- Upstream record
- samber/developer-relations-skills
- Version
- Version 3
- Published
- Publication review
- Approved for publication
- Content fingerprint
1595473ec4f056e88adf923b398d5957cf2495096eba9e834520f20c79298894