Release Review: MultiPointVPN r1.1 (alpha)#28
Release Review: MultiPointVPN r1.1 (alpha)#28camara-release-automation[bot] wants to merge 4 commits into
Conversation
CAMARA Validation — PASS (with warnings)0 errors, 18 warnings, 5 hints | Profile: standard
|
tanjadegroot
left a comment
There was a problem hiding this comment.
Hi team,
you need to complete the Codeowner Actions and tick the boxes after the checks are done. THis will show Release Management that they can review as well.
I checked the release review PR: the changelog needs to be completed as indicated in the temporary text provided (see comment), and one other small fix is needed.
Finally, the Validation process Warnings and applicable Hints need to be fixed.
I recommend fixing them now as they are mostly documentation of the API and some other easy fixes. In that case, do /discard-snapshot, do the updates on main, checl warnings an hints are reduced t only non applicable ones and redo /create snapshot.
However, as a next alpha version pre-release will need to be done using the Spring26 Commonalities r4.3 and ICM r4.2 which will probably detect additional warnings and hints, you may also decide to do these fixes in that next pre-release. In that case, fix my comments on this PR, and merge it after the required approvals, and follow the release instructions in this issue.
Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
2364c1c
Updated changelog to include first alpha version of multi-point-vpn API.
|
/create snapshot |
|
/discard-snapshot |
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
0.1.0-alpha.1Dependencies: Commonalities r3.4, ICM r3.3
Codeowner Actions
1. Update release notes
Do not copy administrative, tooling-only, or internal maintenance changes unless they affect API consumers.
2. Confirm API release readiness
release-plan.yamlinfo.description) is up to date with the API definitionRelease Management Actions
Required release assets per API status
public
public
M = Mandatory, O = Optional — Full documentation
During the automation introduction phase, please also verify the snapshot content: that
release-metadata.yamlis correct, that the generated API version numbers and server URLs (and other version fields and references) are right, and that the README update reflects the release tag and version handling.Valid next actions for codeowners
/discard-snapshot <reason>in the Release Issue to discard this snapshot, return toplanned, and update content onmainSnapshot:
r1.1-528ba29