-
Notifications
You must be signed in to change notification settings - Fork 6
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
V0.2.0 M4 #95
V0.2.0 M4 #95
Conversation
r1.3 added
for r1.3
Remove “-rc.n” from the version and server path: camaraproject#92 Remove "-rc.02" from "x-camara-commonalities": camaraproject#94
Missing "Bold" termination characters (**)
@FabrizioMoggio thanks for the release PR - have created camaraproject/ReleaseManagement#77 for the Release Management review. Please update also the API Readiness checklist and the version within the .feature files as part of the PR. |
@FabrizioMoggio and another important point: The Release Notes for a public release must be in generell a summary of all changes since the last public release, not just the delta to the last release candidate. Note: the "full changelog" link is |
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
Your PR will be used as an example for me for other API Fabrizio :)
Correction for my comment: this @FabrizioMoggio PR will be the example once the comment from @hdamker will be fixed ;) |
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.
- Please update also the API Readiness checklist and the version within the .feature files as part of the PR
- Complete the CHANGELOG for the public release with all updates, see my previous comment
BTW: release tracker updated ... r1.3 will be the public release tag, not the next pre-release. |
version v0.2.0 according to: camaraproject#95 (comment)
according to: camaraproject#98
I’m sorry to ask for advice, I’m trying do to my best 😊 from my holidays. For M4 I should have addressed all your comments. The current PR for the CFS API is targeting the public release. What I’m not sure of is if at 30/08 the public release should be merged (if so, we missed it 😊) or if the final approval from @camaraproject/release-management_maintainers is due for M5 (09-15). |
@FabrizioMoggio thank for taking car during your vacation! No worries, you have done every necessary for the M4 milestone by creating and updating this release PR so far. Indeed, the review and approval by Release Management will happen before M5 and then the merge. @bigludo7 @chinaunicomyangfan Please review the PR and the latest changes as well and approve the PR already. |
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.
the requested changes by @hdamker have been implemented
Dear @hdamker I don't know how to move forward. You requested a change and I have implemented it but I can't find a way to mark the requested changes as implemented. So I can't merge. Is it you that need to control and mark them as implemented? |
including: the changes from: camaraproject#99 implementing issue: camaraproject#100
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
The merge-base changed after approval.
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.
a few broken links and typos to fix and this is OK: LGTM from release mgmt
This is the first official release of the Call Forwarding Signal API, version 0.2.0. It contains mainly alignments with the Commonalities 0.4.0 and the Release Management Guidelines. | ||
|
||
- API definition **with inline documentation**: | ||
- OpenAPI [YAML spec file](https://github.com/camaraproject/CallForwardingSignal/blob/r1.3/code/API_definitions/Call_Forwarding_Signal.yaml) |
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.
All 3 links for API display in this section need to be updated to point to the new file name f the API yaml
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.
Line 19 (location: virtually) can be removed from teh scope section.
- OpenAPI [YAML spec file](https://github.com/camaraproject/CallForwardingSignal/blob/r1.2/code/API_definitions/Call_Forwarding_Signal.yaml) | ||
- [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/CallForwardingSignal/r1.2/code/API_definitions/Call_Forwarding_Signal.yaml&nocors) | ||
- [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/CallForwardingSignal/r1.2/code/API_definitions/Call_Forwarding_Signal.yaml) | ||
- OpenAPI [YAML spec file](https://github.com/camaraproject/CallForwardingSignal/blob/r1.3/code/API_definitions/Call_Forwarding_Signal.yaml) |
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.
All 3 links here need to be updated with the new API file name
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.
Just 2 clarification questions
- on line 229: does unconditional forwarding overwrite conditional forwarding if both are active ?
- on line 230: with "This endpoit exceeds the main scope of the CFS API, for this reason an error code 501 can be returned" do you mean that this second endpoint is optional and may not be provided and that 501 is returned in that case ?
- there is a type in "endpoint" in line 229
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.
Line 132: typo: involked -> invoked
Line 173: typo requst -> request
@@ -1,21 +1,21 @@ | |||
|
|||
# API Readiness Checklist | |||
|
|||
Checklist for API call-forwarding-signal v0.2.0-rc.2 in r1.2 | |||
Checklist for API call-forwarding-signal v0.2.0 in r1.3 | |||
|
|||
|
|||
| Nr | API release assets | alpha | release-candidate | public-release<br>initial | public-release<br> stable | Status | Comments | | |||
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----| | |||
| 1 | API definition | M | M | M | M | Y | /code/API_definitions/Call_Forwarding_Signal.yaml | |
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.
change to new API yaml file name (call-forwarding-signal.yaml)
Closed because EasyCLA problems. Replaced by: #101 |
M4 version for Fall24:
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
final release for Fall24
Which issue(s) this PR fixes:
#94
#93
#96
#97
#98
#100