Release readiness

Passing tests isn't the same as being ready to release. This checklist covers everything else a release depends on: security, licences, signing, the release pipeline, field testing, privacy, documentation, rollback and known limits (#78). It is the gate before 1.0.0, and it's brought up to date before each release, starting with 0.2.0.

How to read it:

• Status: each item is PASS, FAIL, NOT RUN or BLOCKED, from evidence that can be checked: a closed issue, a document, or a command with its result. An item without that evidence is never PASS.

• Owner: the PO decides and holds accounts. The agent keeps the evidence current.

• Gaps: every item that isn't PASS is also in Gaps for the PO. The PO accepts each gap or asks for it to be fixed; nothing is accepted on the PO's behalf.

• Scope: Windows and Linux. macOS isn't planned, and V1 parity acceptance (#85) was closed as not planned (PO decision, 2026-11-05).

Last reviewed: 2026-11-10, for v0.2.0: on main at 7dce4d1, and the advisory check again with #446 in, on the branch for #450.

Security

Licences

Packaging and signing

Release pipeline

Field testing and candidate feedback

Privacy and accessibility

Documentation

Browser extension

Rollback

• Before a release is public: the release workflow makes a draft, and only the PO publishes it (RELEASE_PROCESS.md). A wrong draft is never published; the fix goes into a new candidate.

• After a release: the fix ships in a later version (Choosing the next version). For users, going back to the earlier version, with their data, follows Going back to an earlier version. A database that a newer version upgraded is refused by an older one unchanged, and the backup made before the upgrade restores it (DATA_AND_MIGRATIONS.md).

• The browser extension: each store keeps its own versions. A bad extension version is replaced by a new upload. The app accepts the store's extension ID, which doesn't change between versions.

Known limitations

What users meet in this version, with where it is documented:

• The Windows installer isn't signed: SmartScreen warns on first run (PACKAGING.md).

• The extension is only in the Chrome Web Store in 0.2.0. Edge and Firefox users load it by hand until their stores approve it (Browser integration).

• Nothing is imported from V1 (V1 and Apollo Download Manager).

• Protocols: FTP and SFTP use one connection each, and SFTP and torrents can't use an HTTPS proxy (Protocols).

• Torrents through a proxy have limits (Torrents).

• Snap and Flatpak browsers may not be able to start the browser connection. Settings, Browser warns beside such a browser; the user guide doesn't mention it yet.

• On Linux, browser registrations must be removed before the package (Installing).

• No macOS build.

Gaps for the PO

Each item here needs the PO's decision before the release it blocks: accept it for that release, or have it fixed. Nothing here is accepted yet.