I see currently version of client tools is: > $ oc version > oc v3.0.0.0-32-g3ae1d27 > kubernetes v0.17.1-804-g496be63 Can we have a document with policy to not break backward comatibility between minor releases, maybe the second '0' in that version string? It would be very valuable in scripting to check that available cli tool version is compatible. At the moment I don't know which part of the version string to rely on.
I am not sure if this is a docs bug? Alex - can you comment?
There is probably room for some doc'ing of the expectations around backwards compatibility going forward for the API/CLI. Following up with SMEs.
Work in progress: https://github.com/openshift/openshift-docs/pull/2496
@Clayton, please review: https://github.com/openshift/openshift-docs/pull/2496 Thanks!
@Aleksandar, please review. Thanks!
Hello Ashley, I have put a comment in github some half a month ago but it was not answered. Also originally I proposed to commit Semantic Versioning compatibility (http://semver.org/). I don't see that mentioned in the PR and I assumed we decided to not commit to it. Although I think it is good if we do. Regards.
Commits pushed to master at https://github.com/openshift/openshift-docs https://github.com/openshift/openshift-docs/commit/46b535d8e252e1514857bf9362dd3c87364d0c26 Bug 1235445, added a Versioning Policy https://github.com/openshift/openshift-docs/commit/9cafa6f1c18b389f0d295a925599fb44e2a63585 Merge pull request #2496 from ahardin-rh/versioning-policy Bug 1235445, added a Versioning Policy
Content is now published: https://access.redhat.com/documentation/en/openshift-container-platform/3.3/paged/release-notes/chapter-1-overview