[camara-release-automation]

Release Review: r2.1 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
subscription-status	0.2.0-rc.1	rc	0.1.0

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

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: r2.1-9adaaa9

[camara-validation]

CAMARA Validation — PASS

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

View full results

[eric-murray]

Initial review findings documented in #38.

Nothing major and nothing that would prevent this release as is.

However, you need to update the change log by editing the CHANGELOG-r2.md file in this PR and including relevant changes each section of the template. Review other KYC APIs for guidance on what is expected.

[ToshiWakayama-KDDI]

Thank you, @eric-murray , for the review.

Hi @chinaunicomyangfan , @ClownsAlbert , @ChuanyuChen , @DanXu-ChinaTelecom ,

Please do Update the CHANGELOG to proceed with the release of a RC.

Thanks,

[hdamker]

FYI: This snapshot was created before camaraproject/tooling#431 got active with tooling release v0.10.0. #431 moved the automated README Release Information update from the release-review branch onto the snapshot branch. The merge commit above brings this branch in line with that: the README update now lives on the snapshot branch, so this branch differs from it by the CHANGELOG only. No content change.

[tanjadegroot]

Thank you, @eric-murray , for the review.

Hi @chinaunicomyangfan , @ClownsAlbert , @ChuanyuChen , @DanXu-ChinaTelecom ,

Please do Update the CHANGELOG to proceed with the release of a RC.

Thanks,

Team, please also consider addressing Eric's comments in #38 on main and do a new snapshot for this release. Thanks !

Please also ensure to follow and tick off accordingly the code-owners checklist in the Release Review issue.

After this release-candidiate is published, you can do the next rc for Commonalities r4.4 alignment (this requires updating the release-plan before doing the new snapshot.

[ToshiWakayama-KDDI]

Thank you, @eric-murray , for the review.
Hi @chinaunicomyangfan , @ClownsAlbert , @ChuanyuChen , @DanXu-ChinaTelecom ,
Please do Update the CHANGELOG to proceed with the release of a RC.
Thanks,

Team, please also consider addressing Eric's comments in #38 on main and do a new snapshot for this release. Thanks !

Please also ensure to follow and tick off accordingly the code-owners checklist in the Release Review issue.

After this release-candidiate is published, you can do the next rc for Commonalities r4.4 alignment (this requires updating the release-plan before doing the new snapshot.

Hi @tanjadegroot ,
cc @chinaunicomyangfan , @ClownsAlbert , @ChuanyuChen , @DanXu-ChinaTelecom

Thank you for the guidance. Just to ensure we are perfectly aligned on the next steps, could you please confirm which of the following workflows you intended?

Workflow A:

1. Address Eric's comments from issue Release r2.1 review findings #38 in the main branch via new PR(s).
2. Once that is merged, /discard-snapshot on this PR (Release Review: SubscriptionStatus r2.1 (rc Sync26) #37) and then /create-snapshot on main to generate a new Release Review PR.
3. Update the changelog.md file within that new PR and merge it. This will publish the first RC.
4. After that, begin work on the Commonalities r4.4 alignment for the second RC.

OR

Workflow B:

1. Update the changelog.md in this current PR (Release Review: SubscriptionStatus r2.1 (rc Sync26) #37) and merge it. This will publish the first RC.
2. After that, address Eric's comments from issue Release r2.1 review findings #38 and the Commonalities r4.4 alignment in subsequent PR(s) for the second RC.

Your clarification would be greatly appreciated. Thanks!

[eric-murray]

Hi @ToshiWakayama-KDDI

It is up to the API team, but I would recommend Workflow B so that the M3 requirement is satisfied for this API.

If you tag me when the change log is updated, I will approve this PR.

[tanjadegroot]

@ToshiWakayama-KDDI will you do the changelog update so we can proceed to M3 please ? Let me know if you need any help.

[ToshiWakayama-KDDI]

Just to add a PR #36 here is enough, I believe:

• Align subscription-status with Sync26 RC requirements by @chinaunicomyangfan in Align subscription-status with Sync26 RC requirements #36

[ToshiWakayama-KDDI]

@ToshiWakayama-KDDI will you do the changelog update so we can proceed to M3 please ? Let me know if you need any help.

Thanks, @tanjadegroot . I have just tried, but it seems I can't do it because I have no wirte access to this API. I have jsut left a comment to the line where text about PR #36 should be added, and I believe this is only the change needed. I will send an email to @chinaunicomyangfan for heads-up.

BR

[chinaunicomyangfan]

@ToshiWakayama-KDDI Thanks for flagging this! The CHANGELOG has been updated, ready for re-review.

[chinaunicomyangfan]

@eric-murray CHANGELOG has been updated, ready for re-review. Thanks!

[ToshiWakayama-KDDI]

Thanks, @chinaunicomyangfan .

Please don't forget to tick the above three points ( Update the CHANGELOG, Document deferred validation warnings (and hints), The release is ready for Release Management review ) to show you have confirmed them.

BR

[eric-murray]

Approving release candidate for publication on behalf of Release Management

[ChuanyuChen]

looks good to me.

[tanjadegroot]

Hi team, please check and tick the "Codeowner Actions" to complete the review process and proceed to merge.
Then please do not forget to go back to the Release Issue #34 and do the final action "/publish-release --confirm r2.1"

many thanks !

[tanjadegroot]

Hi team, please proceed to M3 by

1. merging this PR and
2. go to Release r2.1 (RC) — Sync26 #34 and do /publish-release --confirm r2.1

After that please address on main

• merge the post-publication PR generated by automation
• update release-plan.yaml to target_release_tag: r2.2 and commonalities_release: r4.4
• Do Commonalities r4.4 alignement per guidelines
• update per review feedback from Release r2.1 review findings #38

And then snapshot r2.2; update the changelog; check and tick the "Codeowner action" boxes.

Many thanks !

[chinaunicomyangfan]

Thanks, @chinaunicomyangfan .

Please don't forget to tick the above three points ( Update the CHANGELOG, Document deferred validation warnings (and hints), The release is ready for Release Management review ) to show you have confirmed them.

BR

@ToshiWakayama-KDDI Thanks for the reminder! The three checkboxes have been ticked. Validation shows 0 errors/warnings/hints, so no deferred items to document.