Conversation
|
@jgarciahospital See my comments above. I assumed in my comments that this will be indeed a release candidate of v0.1.1. Being directly the patch release of v0.1.0 could be another option. If the changes are done, please add @camaraproject/release-management_maintainers as reviewer. |
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
|
API definition:
|
Updating Authorization and authentication info section according to las I&CM version
|
@hdamker ready for new revision of this fields
Also added #42 for documentation and included in changelog, as agreed in followup meeting#12 |
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
hdamker
left a comment
There was a problem hiding this comment.
Looks good from Release Management. Please proceed with the release.
Thanks @hdamker. As no other codeOwner active (holidays), may you validate the PR? |
I can bypass the rule protection and merge, but would be good if at least one further Sub Project participant would approve the PR before, @gregory1g maybe? |
| termsOfService: http://swagger.io/terms/ | ||
| contact: | ||
| email: project-email@sample.com | ||
| (FAQs will be added in a later version of the documentation) |
There was a problem hiding this comment.
why add "TBD" entry to the released version of the spec?
There was a problem hiding this comment.
This line was copied over from the very first API documentations. A FAQ was never mandatory, even not in the outdated documentation template (which will now get deprecated). So you can delete this line.
There was a problem hiding this comment.
I have removed it PR #42 . And now it is added back.
|
@hdamker ready now? |
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Prepare the release 1.1 with the required changes to support meta guidelines