-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2.2 #388
Release 2.2 #388
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-authored-by: Pedro Díez García <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Pedro Díez García <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi all,
please check some comments for clarifications and a few alignment point from the Release Mgmt team.
please check an handle as appropriate. after that RM can approve and /LGTM
in /documentation line 40 and 42 should have relative links per the release |
documentation
these changes can be done later as needed. Up to the team. |
documentation this file is very 3GPP focussed. it could be more logically placed in supporting documents (and even more logically in ICM ...) Not sure if there is a reference to it somewhere. Also inside the file terminology could be aligned (API invoker -> API consumer, UE -> device, etc), depending on the objective of this document. Decision up to the team. |
documentation line 26 - is this reference still valid (e.g. it refers to API families), or should it point to the latest version of the CAMARA presentation (in the marketing or governance repo) or should there be an update created ? btw, this same file is also in the local supporting documents folder, so maybe the link should point there ? (and updates would be there as well). |
There are 2 open PRs labeled with Spring25 - should these go into the release 2.2 or later ? |
Yes labeled, but not planned in the r2.2 |
Issue #394 |
Issue #396 |
Issue #397 |
Thank you @tanjadegroot for thorough review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Rafal for the responses and updates.
LGTM from Release Management !
Don't forget to update the meta-release page with the new release tag and associated M2 date
here https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14560849/Meta-release+Spring25
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What type of PR is this?
What this PR does / why we need it:
This is Release PR for release 2.2 containing version v0.5.0-rc.1 of Commonalities
Which issue(s) this PR fixes:
Fixes #384
Does this PR introduce a breaking change?
Special notes for reviewers:
Changelog input