Release Review: EdgeApplicationManagement r1.2 (rc Sync26)

[camara-release-automation]

Release Review: r1.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
edge-application-management	0.1.0-rc.1	rc

Dependencies: Commonalities r4.3, ICM r4.2

Codeowner Actions

Tick each box once done. Release Management review starts when all three boxes are ticked.

• Update the CHANGELOG

  What to do:

  • Copy all API-consumer-relevant changes from the provided list into the appropriate Added / Changed / Fixed / Removed sections for each API.
  • Do not copy administrative, tooling-only, or internal maintenance changes unless they affect API consumers.
  • Check which kinds of changes must be listed for this release type — the rules are stated at the top of the CHANGELOG file and are easily overlooked.

• 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

• 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: r1.2-e3c2aff

[camara-validation]

CAMARA Validation — PASS

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

View full results

[tanjadegroot]

Hi team,

please be aware that new APIs should first do a full release cycle up to their public release on the independent track.

I see you have jumped over to the meta-release track, so please do

• /discard-snapshot on this issue
• on main, revert back the release-plan.yaml to the independent track for doing your next rc pre-release

Then stay on the independent track until you have done your first public release. After that you can decide to continue on the independent track still or to join a meta-release.

Please address as much as possible the hints provided by the validation process.

@hdamker in case of any issues with changing release track back from meta-release to independent.

Dismissing approve since we should be in the independent track.