Version and release rules#

PRISM has its own version sequence. Its version does not follow the AOTX backend version. Record supported backend versions separately when integration is tested.

VERSION is the source version. Package metadata and the application version display agree with it. Version 0.1.0 is publicly available as an early source release in the PRISM repository.

Version changes#

Use MAJOR.MINOR.PATCH version numbers.

• Increase PATCH for compatible fixes.
• Increase MINOR for features. Before version 1.0, use MINOR for incompatible changes too.
• After version 1.0, increase MAJOR for incompatible changes.
• Use a suffix such as -rc.1 for a release candidate when needed.

Keep pending changes under Unreleased in the changelog. Group changes by usable behavior. Do not publish development records or estimates.

Versioned package release sequence#

1. Prepare the version and changelog on a working branch.
2. Complete the relevant checks and independent review.
3. Merge the release pull request into master.
4. Verify the accepted source commit and package contents.
5. Create an annotated tag such as v0.1.0 on that commit.
6. Publish the release with matching versioned artifacts and checksums.

Tags and publication require explicit release authorization. Do not move a published tag or replace published artifacts with different bytes. Publish a new version for a correction.

Packages include their source identity, dependency notices and checksums. Test installation and upgrade behavior before publication. Release status must distinguish source checks from complete application acceptance.

The source repository is public. Versioned package releases follow the checks and publication procedure above.