Release Review: EdgeApplicationManagement r1.2 (rc)

[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	Comparison target
edge-application-management	0.1.0-rc.1	rc	N/A

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

[camara-validation]

CAMARA Validation — PASS

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

View full results

[DLondonoD]

The remaining hints are explained in the issue #65

[eric-murray]

Hi @JoseMConde

Regarding the change log, the notes at the top of the change log state:

The below sections record the changes for each API version in each release as follows:

• ...
• for the first release-candidate, all changes since the last public release
• ,,,

As there is no "last public release" for this API, everything is essentially new (i.e. Added) relative to nothing at all. There are no breaking changes, nor has anything been fixed, changed or removed.

I'd suggest to slim down the change log considerably, focusing only on the features (endpoints and functionality) that have been defined for this API. Potential API consumers are not really interested in the API design evolution that preceded the first public release.

[JoseMConde]

Hi @JoseMConde

Regarding the change log, the notes at the top of the change log state:

The below sections record the changes for each API version in each release as follows:

• ...
• for the first release-candidate, all changes since the last public release
• ,,,

As there is no "last public release" for this API, everything is essentially new (i.e. Added) relative to nothing at all. There are no breaking changes, nor has anything been fixed, changed or removed.

I'd suggest to slim down the change log considerably, focusing only on the features (endpoints and functionality) that have been defined for this API. Potential API consumers are not really interested in the API design evolution that preceded the first public release.

Hi @eric-murray , Thanks for the comment.
I updated acordanly, please let me know if it is OK now.
Is there any other issue or are you still reviewing??