Releases

A clear identity
for every release.

Stage describes readiness. Version identifies the candidate. Public release notes will describe the package people can actually download.

No public package is listed yet.

Public downloads are not open. Internal Pre-alpha 0.0.1 development builds are the reported baseline for this website foundation. The first reviewed release is planned as Alpha; its numeric version and date are not selected here.

One candidate, one version.

Windows and macOS built from the same candidate share one stage and numeric version. Stage changes do not reset numbering. Documentation-only changes do not create a new application version.

An update should not silently replace a distributed numbered package with different code. Package provenance, requirements and amendments belong alongside the release notes.

Release notes should answer useful questions.

  1. Who is the reviewed package for, and what workflows are included?
  2. What changed in visible behaviour?
  3. Which defects were corrected and what limits remain?
  4. Which systems, Resolve editions/routes and clients were checked?
  5. Does installation/update or project migration change?
  6. Which guides and examples match this package?

Historical development checks remain dated evidence. They are not fresh qualification for a later package.

Follow development separately.

Development direction and source-reviewed feature descriptions live in Progress. The website’s own changes are recorded separately from application releases; completing these pages does not announce a new app package.