Release Cadence

Tracks formal releases over the last 90 days.

Methodology

What We Look For

Formal releases demonstrate shipping discipline and product maturity.

Evaluation Criteria:

• Releases/tags created in last 90 days
• Quality of release notes/changelogs
• Semantic versioning practices
• Meaningful changes (not just version bumps)

Data Sources:

• GitHub API - Releases
• GitHub releases tab
• NPM, PyPI, or other package registries

Significance

Regular releases indicate:

• Shipping discipline
• Mature development process
• Clear versioning strategy
• Customer-facing updates

Guide

Finding Information

Step 1: Check GitHub Releases

For each repository:

• Navigate to the "Releases" tab
• Count releases in the last 90 days
• Review release notes

Step 2: Verify Package Registries

If you publish packages:

• Check NPM, PyPI, RubyGems, etc.
• Count published versions in last 90 days
• Ensure versions match GitHub releases

Step 3: Assess Release Quality

For each release:

• Does it have release notes?
• Are changes documented?
• Is it a meaningful update?
• Does it follow semantic versioning?

Submitting Evidence

When submitting release cadence:

1. Release Count: Total releases in last 90 days

2. Repository URLs: Links to release pages

3. Package Links (if applicable): NPM, PyPI, etc.

4. Release Strategy: Description of your release process