-
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
Update versioning section in api design guidelines #215
Update versioning section in api design guidelines #215
Conversation
update of version section step 1
section 5. Version - update 3 update of TOC
…o tanjadegroot-patch-1
Update API-design-guidelines.md
final adjustments
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.
Looks good to me. One proposal and one question below.
Co-authored-by: Herbert Damker <52109189+hdamker@users.noreply.github.com>
Update following comments on backward compatibility section
I have discovered that in Commonalities we have https://github.com/camaraproject/Commonalities/blob/main/documentation/Camara_Versioning_Guidelines.md |
Hi Rafal, yes that is correct. this file can be deprecated. |
Tanja, if you could modify the file in Nokia fork: https://github.com/nokia/camaraproject-Commonalities/blob/Update-versioning-section-in-API-design-guidelines/documentation/Camara_Versioning_Guidelines.md then we go with all the changes within this PR. |
Changed the use of "public-release" to just "public" Removed references to release aspects for the versioning section
@hdamker to check this update |
I just need to remove the file corrrect ? |
release mgmt information is moved to the Release Mgmt repo
@tanjadegroot that's not enough, also the line in the table within https://github.com/camaraproject/Commonalities/blob/main/README.md need to be updated/replaced. What about deleting the two lines about API-Readiness-Checklist.md and Camara_Versioning_Guidelines.md and put underneath the table something like:
@rartych WDYT about the README? |
complement to removing release info from versioning section
removed the references to 2 removed documents and added note to point to ReleaseManagement repo
README.md update done |
Shilpa's comment on URL version
included updates on removing"-" in release names some more tweeks
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.
/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.
/LGTM
0556740
fix typo Co-authored-by: Pedro Díez García <pedro.diezgarcia@telefonica.com>
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.
/LGTM
@patrice-conil Could you approve it? |
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?
Add one of the following kinds:
What this PR does / why we need it:
It updates the versioning section to be in line with the API versioning for the release management process
Which issue(s) this PR fixes:
Fixes #206
Special notes for reviewers:
Changelog input
Additional documentation
This section can be blank.