Release guide

Know the stage.
Know the scope.

A stage label helps you interpret a candidate. The actual supported workflow and environment still need explicit evidence.

Pre-alpha: internal development.

Pre-alpha identifies an internal development candidate. Features, interface behaviour and delivery paths may change. The reported foundation identity is Pre-alpha 0.0.1; internal build existence does not make a public supported download.

Alpha: a reviewed evolving product.

The first reviewed friend/public package is planned as Alpha. Primary features can still evolve or arrive later. Alpha is a readiness decision for the stated trial scope, not a declaration that the long-term product is complete.

Later stages need their own decision.

Beta and Stable require an agreed readiness decision for the workflows being advertised. A numeric version alone does not infer either stage, and neither stage implies completion of every future idea.

Read qualification per combination.

  • Exact distributed package and candidate identity.
  • OS, architecture, hardware and lifecycle checks.
  • Actual Resolve edition/version/transport and editable output.
  • Named client setup, inspection, revision and recovery.
  • Known issues, instructions and content rights.

Unavailable or untested combinations stay unqualified. Test totals, compile success and development screenshots cannot substitute for these records.