Governance

Versioning

Purpose

ICC DSL is expected to change frequently. The site therefore treats every language release as a separate artifact, not as a mutable page.

Version Families

• Language releases live in src/content/releases/.
• Editorial pages live in markdown or Astro pages.
• Site implementation lives in components, layouts, and styles.

This separation allows multiple daily copy edits, site edits, and language additions without mixing responsibilities.

Version Numbers

Use internal semantic versioning:

vMAJOR.MINOR.PATCH

The public label may stay compact, for example v1.01.

Change Rules

• Additive syntax, new reference forms, or new commands: new minor release.
• Clarifications or typo fixes: patch release or errata.
• Breaking grammar or incompatible meaning: new major release.
• Published release pages should not be silently rewritten. Add a successor release instead.

Editorial Workflow

Recommended branches:

language/v1.02
editorial/abstract-copy
site/navigation-update

Recommended commit scopes:

language: add ICC DSL v1.02
editorial: clarify prompt-engineering transition
site: refine contact form layout

Release Checklist

1. Add a new release markdown file.
2. Include frontmatter: slug, title, version, label, status, date, stability, summary.
3. Mark the prior release as superseded when appropriate.
4. Build the site.
5. Commit language release and site rendering changes together only when both are required.