Release r1.1 with 0.1.0-rc.1 version (Fall'25 M3)#17
Release r1.1 with 0.1.0-rc.1 version (Fall'25 M3)#17Kevsy merged 27 commits intocamaraproject:mainfrom
Conversation
|
LGTM |
As per API versioning guidelines "For initial public API versions 0.y.z, the MINOR number MUST be included in the URL, e.g. v0.y. "
Kevsy
left a comment
There was a problem hiding this comment.
LGTM (I fixed the version number in the URL, see above)
|
Please touch also the version within the feature file |
|
documentation/API_documentation/Optimal-Edge-Discovery-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
Kevsy
left a comment
There was a problem hiding this comment.
A couple of minor changes (see above) otherwise LGTM
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
…diness-Checklist.md Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
…dge-discovery-API-Readiness-Checklist.md
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
hdamker
left a comment
There was a problem hiding this comment.
Two small suggestions which you can directly commit.
Almost there!
|
@urvika-v I will again approve when you have committed the suggestions. |
There was a problem hiding this comment.
Have committed my suggestions from #17 (review) to be able to finally approve from Release Management side.
Next steps for @camaraproject/optimal-edge-discovery_codeowners
- PR approved and merged (by API repository codeowner)
- Release created within GitHub (by API repository codeowner)
- Release Tracker updated (with creation date of the release and the release tag link)
|
Codeowner tasks completed, closing issue |
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Publication of Fall'25 M3 release candidate v0.1.0-rc.1
Which issue(s) this PR fixes:
Fixes #
Special notes for reviewers:
None
Changelog input
Additional documentation
This section can be blank.