Record that 0.6.0 ships without a field pass - #27
Merged
Conversation
The run record said 0.6.0 must not be tagged until the table was filled in. It is being tagged anyway, on the maintainer's decision, so the file says that instead of carrying a rule the release breaks — and instead of leaving an empty table that reads as a pass to whoever opens it next. The changelog carries the same note, which is what RELEASING.md asks for when the field pass is skipped: say so in the release notes rather than leaving it ambiguous. It lands in the GitHub release body from there. What is actually unverified is named rather than implied: the answer path, the push path, the audio session, the call teardown and the registration lifecycle, none of which the unit suite reaches. The decline-path fix in particular came from a field report and has never been confirmed in the field. The table stays open for whenever the pass happens.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 0.6.0 run record said the tag must not be cut until its table was filled
in. It is being cut anyway, on the maintainer's decision, so the file records
that rather than carrying a rule the release breaks — and rather than leaving
an empty table that the next reader takes for a pass.
RELEASING.mdasks for exactly this when the field pass is skipped: say so inthe release notes instead of leaving it ambiguous. The changelog note lands in
the GitHub release body from there.
What is unverified is named rather than implied — the answer path, the push
path, the audio session, the call teardown and the registration lifecycle, none
of which the unit suite reaches. The decline-path fix came from a field report
and has never been confirmed in the field.
Docs only; no code changes. The table stays open for whenever the pass happens.