Skip to content

Record that 0.6.0 ships without a field pass #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PetrShtuka merged 1 commit into from
Aug 25, 2026
Merged

Record that 0.6.0 ships without a field pass #27

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Empty file added 0."
View file
Open in desktop
Empty file.
7 changes: 7 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,13 @@ bump may contain breaking changes, and each one is listed below.

## [0.6.0] - 2026-08-24

> **Not field-tested.** This release ships on its automated suite alone —
> 131 tests, thread sanitizer, device and strict-concurrency builds, podspec
> lint. The on-device pass in `FIELD-TESTING.md` was not run, so the answer
> path, the push path, the audio session, the call teardown and the
> registration lifecycle are unverified against a real PBX. See the 0.6.0 run
> record in that file.

### Fixed

- A call declined while it was still ringing could leave the PBX with the call
Expand Down
24 changes: 18 additions & 6 deletions FIELD-TESTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,12 +19,24 @@ as the regression matrix for Majordom deployments and future releases.

## 0.6.0 run record

**Status: not run. 0.6.0 must not be tagged until this table is filled in.**
Nothing below may be ticked off from the Simulator, from a code reading or from
a green CI run — none of those exercise PushKit, the lock screen or a real audio
route, which is the entire reason this file exists. Fill the table in on the
device and commit it before the tag. An empty record is the honest state of the
release; an invented one is worse than no record at all.
**Status: not run. 0.6.0 was tagged without it**, on the maintainer's decision
of 2026-08-25. This is a deliberate exception to step 0 of `RELEASING.md`, not
an oversight, and it is written down here rather than left as an empty table
somebody later reads as a pass.

What that means concretely: 0.6.0 ships with its automated suite green — 131
tests, thread sanitizer clean, device and strict-concurrency builds, podspec
lint — and with **no on-device verification of the answer path, the push path,
the audio session, the call teardown or the registration lifecycle.** The unit
suite reaches none of them. The largest behavioural change in the release, the
decline-path fix, was made from a field report and has never been confirmed in
the field.

The table below stays open. Fill it in whenever the pass happens, on 0.6.0 or
on whatever ships next, and move this note to match. Nothing below may be
ticked off from the Simulator, from a code reading or from a green CI run —
none of those exercise PushKit, the lock screen or a real audio route, which is
the entire reason this file exists.

Since the last recorded pass (0.4.0, 2026-08-04) the answer path, the audio
session, the call teardown and the account configuration have all moved, so this
Expand Down
Loading