Skip to content

Release Review: MultiPointVPN r1.1 (alpha)#28

Closed
camara-release-automation[bot] wants to merge 4 commits into
release-snapshot/r1.1-528ba29from
release-review/r1.1-528ba29
Closed

Release Review: MultiPointVPN r1.1 (alpha)#28
camara-release-automation[bot] wants to merge 4 commits into
release-snapshot/r1.1-528ba29from
release-review/r1.1-528ba29

Conversation

@camara-release-automation

@camara-release-automation camara-release-automation Bot commented May 29, 2026

Copy link
Copy Markdown
Contributor

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
multi-point-vpn 0.1.0-alpha.1 alpha

Dependencies: Commonalities r3.4, ICM r3.3

Codeowner Actions

1. Update release notes

  • CHANGELOG updated: copy all API-consumer-relevant changes into the appropriate Added / Changed / Fixed / Removed sections for each API as needed.
    Do not copy administrative, tooling-only, or internal maintenance changes unless they affect API consumers.

2. Confirm API release readiness

  • API version(s) used in all files match release-plan.yaml
  • API documentation (info.description) is up to date with the API definition

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
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

During the automation introduction phase, please also verify the snapshot content: that release-metadata.yaml is 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

  • 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-528ba29

@camara-validation

camara-validation Bot commented May 29, 2026

Copy link
Copy Markdown

CAMARA Validation — PASS (with warnings)

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

View full results

Warnings SHOULD be documented in one or more issues before this release — see the Codeowner Actions in the PR description.

abd-abhisek
abd-abhisek previously approved these changes May 29, 2026

@hemantagogoi-infy hemantagogoi-infy left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@tanjadegroot tanjadegroot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread CHANGELOG/CHANGELOG-r1.md Outdated
Comment thread CHANGELOG/CHANGELOG-r1.md Outdated
Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
@hemantagogoi-infy hemantagogoi-infy dismissed stale reviews from abd-abhisek and themself via 2364c1c June 12, 2026 07:01
Updated changelog to include first alpha version of multi-point-vpn API.
@hdamker hdamker requested a review from tanjadegroot June 12, 2026 07:26
@hemantagogoi-infy

Copy link
Copy Markdown
Contributor

/create snapshot

@hemantagogoi-infy

Copy link
Copy Markdown
Contributor

/discard-snapshot

@camara-release-automation camara-release-automation Bot deleted the release-review/r1.1-528ba29 branch June 12, 2026 12:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants