[camara-release-automation]

Release Review: r3.2 rc

This PR finalizes the reviewable release content for the active snapshot.

Edit and review this PR before merging it into the release snapshot. After Codeowner and Release Management approval, merging this PR creates the draft release.

Release contents

API	Version	Status	Comparison target
network-access-devices	0.3.0-rc.2	rc	0.3.0-rc.1
network-access-domains	0.3.0-rc.2	rc	0.3.0-rc.1

Dependencies: Commonalities r4.3, ICM r4.2

Codeowner Actions

Tick each box once done. Ticking the last box — "The release is ready for Release Management review" — starts the Release Management review.

• Update the CHANGELOG

  What to do:

  • Copy all API-consumer-relevant changes from the provided list into the appropriate Breaking changes / Added / Changed / Fixed / Removed sections for each API. List breaking changes both in Breaking changes and in their normal change category.
  • Do not copy administrative, tooling-only, or internal maintenance changes unless they affect API consumers.
  • For each API, fill the CHANGELOG against the stated comparison target, following the release-type rules at the top of the CHANGELOG.

• Document deferred validation warnings (and hints)

  What to do:

  • Check the CAMARA Validation comment on this PR for warnings and hints.
  • For each warning you do not fix, document it in an issue: include a copy of the validation summary line(s) and the reason the fix is deferred.
  • Document in the same way any validation hint that is applicable to the API and needs to be fixed later.
  • You may group several findings into one issue or split them across issues — either is fine.
  • List the documenting issue(s) in a comment on this PR.
  • Note: documenting deferred warnings is optional but recommended for alpha pre-releases, and mandatory for rc pre-releases and public releases.

• The release is ready for Release Management review

  Check that:

  • All mandatory release assets for the declared status(es) are present (see the table below "Required release assets per API status" by expanding the arrow);
  • API documentation and test cases are adequate for the target status.

  Tick this box to confirm readiness and to start the Release Management review.

Release Management Actions

The following actions and checks are done by a Release Management reviewer before approving the PR:

• Assign the Release Management reviewer(s) as assignee(s) of this PR
• CHANGELOG follows the release documentation rules
• Breaking changes are documented and version updates follow SemVer rules
• Mandatory release assets are present for each API according to its status
• All remaining validation warnings are documented in issues and the reasons for deferral are defensible
• Content findings needing a main PR are collected as sub-issues of one issue titled Release r3.2 review findings (see Recording review findings)

Required release assets per API status

Nr	Asset	alpha	rc	initial public	stable public
1	Release Plan	M	M	M	M
2	API Definition(s)	M	M	M	M
3	Commonalities compliance	O	M	M	M
4	API Documentation	M	M	M	M
5	User Stories	O	O	O	M
6	Test Cases (basic)	O	M	M	M
7	Test Cases (enhanced)	O	O	O	M
8	API Description	O	O	M	M

M = Mandatory, O = Optional — Full documentation

Valid next actions for codeowners

• Merge this PR when all Codeowner Actions and Release Management Actions are complete and the required approvals are present — creates the draft release
• Use /discard-snapshot <reason> in the Release Issue to discard this snapshot, return to planned, and update content on main

---

Snapshot: r3.2-d086eae

[camara-validation]

CAMARA Validation — PASS

0 errors, 0 warnings, 59 hints | Profile: standard

View full results

[eric-murray]

Review findings are documented in issue #200

This release would pass the M3 gate for Sync26, but not the M4, which requires compliance with Commonalities r4.4

You can discard this snapshot and update the release plan for Commonalities r4.4. Or I can approve this as an intermediate release candidate, but at least one more release candidate will be required before the public release. Up to you.

[clundie-CL]

Review findings are documented in issue #200

This release would pass the M3 gate for Sync26, but not the M4, which requires compliance with Commonalities r4.4

You can discard this snapshot and update the release plan for Commonalities r4.4. Or I can approve this as an intermediate release candidate, but at least one more release candidate will be required before the public release. Up to you.

@eric-murray Thank you for your review. My apologies, I must have missed the r4.4 requirement. When did r4.4 become a requirement for M4 out of curiosity? I notice that r4.4 landed in September and I was on a long vacation most of that month and wondering if I missed the notification then.

My understanding is that Sync release cycles are to synchronize to the prior Signal release earlier this year, which I understood to be r4.3. Was this a deviation from the norm Signal -> Sync intent?

Additionally, @hdamker: Would this be a sensible CI feature? In other words, could declaring r4.3 when r4.4 is the expectation be flagged earlier and loudly? This is certainly my fault for not knowing the expectation, but could help identify this discrepancy before getting to the release management review stage prematurely.

[hdamker]

Additionally, @hdamker: Would this be a sensible CI feature? In other words, could declaring r4.3 when r4.4 is the expectation be flagged earlier and loudly? This is certainly my fault for not knowing the expectation, but could help identify this discrepancy before getting to the release management review stage prematurely.

That is a good idea - would you open an issue in ReleaseManagement to describe the potential evolution?

Regarding the change from r4.3 to r4.4 for Sync26 ... r4.4 was originally planned as a patch release of the Spring26 release of Commonalities, as the use of the r4.3 has shown some shortcomings, especially regarding the references into the common files (which were introduced late in r4.3 and actually only halfway). Due to the amount of changes we decided then to declare it not as patch but as a new minor version (0.8.0 -> 0.9.0).

The need to align with r4.4 was announced two times on the codeowners mailing list, here and here.

Hope you will still be able to make the necessary changes.

cc: @tanjadegroot