You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assign this issue to yourself and follow the below list.
For any review action, review the file(s) in the issue/PR listed above.
Put comments in the above issue or PR if they concern non-changed files/text.
Put a short summary of the main review result here into the review issue.
API definition files (YAML) (check version in info & servers objects)
test file(s) availability
changelog updated
readme updated (enforce correct release number / API version naming)
API readiness checklist(s)
Release actions
Assign this issue to yourself or another RM team member and follow the below list.
When done, tick the box in this issue.
API release tracker available on wiki
Review comments addressed (by Sub Project)
Release PR approved (on behalf of Release Management)
PR merged (by Sub Project codeowner)
Release created within GitHub (by Sub Project codeowner)
Release Tracker updated (with creation date of the release and the release tag link)
@hdamker I checked the release tracker and there was one bug: for the qod-provisioning, the tracker title was not updated, nor the API versio. The the Target version was updated while it should not be.
I correct these points on the tracker
btw there was no scope issue link in the qod-provisioning release tracker.
I figured the scope is in the same issues as for qod and qos-profiles e.g. camaraproject/QualityOnDemand#292 ? so I have added that.
if NOK, please comment here. @hdamker
Release PR or issue to review
Review actions
Assign this issue to yourself and follow the below list.
For any review action, review the file(s) in the issue/PR listed above.
Put comments in the above issue or PR if they concern non-changed files/text.
Put a short summary of the main review result here into the review issue.
Release actions
Assign this issue to yourself or another RM team member and follow the below list.
When done, tick the box in this issue.
Additional comments
The text was updated successfully, but these errors were encountered: