Release Review: eSimRemoteManagement r1.1 (alpha)

[camara-release-automation]

Release Review: r1.1 alpha

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
esim-remote-management	0.1.0-alpha.1	alpha	N/A

Dependencies: Commonalities r4.4, 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 r1.1 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: r1.1-66a6842

[camara-validation]

CAMARA Validation — PASS

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

View full results

[ChinaUnicomXiaoDongrui]

@hdamker @eric-murray hello everyone, I'm very glad to see that Commonalities r4.4 has been released. You have made great contributions. During this period, we have made revisions and updates in response to the opinions you raised, specifically addressing the following issues:

issues 30:
We have added callback definitions to the API for asynchronous operations, such as downloading profiles and starting profiles, etc.
According to the requirements of the API, we have supplemented the declaration of Required for the request attribute.
Regarding the issue of unnecessary path prefixes/profiles, we have made deletions, making the modification more concise.
The clientId parameter naming has been replaced to resolve the conflict with OAuth2/OIDC.
Opcodes are represented by strings, such as "SUCCESS" and "ENABLE".
The unused error response codes of the API have been deleted, and the format of the error response codes has been standardized at the same time.
7./profile/oper has been split into three apis: /enable-profile, /disable-profile, and /delete-profile.
Delete the unnecessary parameter timestamp.

issues 31:
1.We have reorganized and updated the API. Currently, the API covers the entire lifecycle, including download, query, enable, disable, and delete.
2.Reference the common definition of CAMARA_common.yaml instead of the local duplicate definition.

At the same time, based on the suggestions of this pr33 , we have fixed the issues of ApiEventType, ApiNotificationEvent, and CloudEvent. Additionally, we have added the definition of notificationsBearerAuth. The Commonalities release in our releaseplan.md has also been modified to 4.4. We hope you can Review it again and raise other questions. Thank you.

In the future, we will synchronously update other files (such as test file) based on the modified yaml file. @SentianSun

[ChinaUnicomXiaoDongrui]

@hdamker @eric-murray hi, I hope this pr can be helpful for the review. Besides, if our other documents can be updated, we will complete the update of the other documents as soon as possible. Thank you.

[hdamker]

Created new finding #37 ... not blocking for this rc, but need to be addressed before public release.

[ChinaUnicomXiaoDongrui]

Created new finding #37 ... not blocking for this rc, but need to be addressed before public release.

@hdamker thanks. We will fix these problems as soon as possible based on the suggestions.