Releases and compatibility

These pages describe what each release delivered, how it was verified, and which compatibility promises apply. They are records: a report describes the release it belongs to and is not updated afterwards.

Compatibility and process

• ABI policy — the native compatibility contract, ownership rules, threading, and the history of C ABI versions.

• Release checklist — how a release is prepared, verified, and tagged.

• Roadmap — the direction of upcoming releases.

Release records

• PostProject 0.9 / ABI 57 qualification — ABI-57 candidate qualification, packages and limits.

• PostProject 0.9 development qualification — the initial ABI-53 development qualification.

• PostProject 0.8 qualification — delivered behavior, qualification and artifact scope.

• PostProject 0.8 exchange conformance — local protocol, crash recovery and independent fixture evidence.

• PostProject 0.8 compatibility evidence — installed family use and review limits.

• PostProject 0.7 candidate acceptance — release qualification and package scope.

• PostProject 0.7 compatibility evidence — family usage and qualification limits.

• PostProject 0.6 candidate acceptance report — acceptance and artifact scope.

• Release 0.6 integration findings — pilot selection and reproduced defects.

• Compatibility-family usage evidence — generated family usage and dependency closure.

• PostProject 0.6 compatibility decision — approved C++ source compatibility scope.

• Release 0.5 acceptance report — release 0.5 acceptance report.

• PostProject 0.5 integration findings — evidence and limitations from the maintained shared-production scenario.

• PostProject 0.5 evidence review — compatibility-family matrix findings and the minimum-pilot decision.

• Compatibility-family usage evidence — generated family-to-host usage matrix.

• PostProject 0.5 compatibility decision — semantic review and accepted release-series decision.

• PostProject 0.5 Ardour pilot evidence — installed-package, C++ exception, and audio-resolver evidence.

• Release 0.4 acceptance report — release 0.4 acceptance report.

• Release 0.4 integration findings — what the Kdenlive and Blender pilots taught during release 0.4.

• Release 0.3 acceptance report — release 0.3 acceptance report.

• Release 0.3 integration findings — what the release 0.3 integrations taught.

• Release 0.3 standards-impact check — release 0.3 standards-impact check.

• Release 0.2 acceptance report — release 0.2 acceptance report.

• Release 0.1 acceptance report — release 0.1 acceptance report.