-
Notifications
You must be signed in to change notification settings - Fork 1.5k
docs/user/versioning: Document APIs covered by our Semantic Versioning #935
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
Conversation
docs/user/overview.md
Outdated
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.
Changing "target" -> "asset" here gets us closer to the wording we use for --dir.
^^ @crawford |
|
Can you rebase this so we can get this in? |
Rebased onto master with a017e43 -> 8df754a. |
Also roll the tips-and-tricks docs into the overview's multi-invocation docs, since they'd been covering the same ground with slightly different wording before. I've expanded the unified description to go into a bit more detail and tie in the new versioning docs. I've also documented the manifest-templates target from 166a9f1 (pkg/asset: new target manifest-templates, 2018-10-30, openshift#592). And I've shifted a few "target directory" references to "asset directory", since that's the language we use for --dir (as shown by --help).
|
Prow seemed hung ("shellcheck Expected — Waiting for status to be reported" and similar), so I've pushed 8df754a -> 28592d0 with a new commit date. |
|
/approve |
|
/retest |
|
Finally all green :). |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: crawford, wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Through eb781ff (Merge pull request openshift#935 from wking/api-stability, 2019-01-04).
I'd added these in 28592d0 (docs/user/versioning: Document APIs covered by our Semantic Versioning, 2018-12-17, openshift#935). But v0.16.1 was the last installer release. Since then, OpenShift tooling picks whatever the most recent commit is in the appropriate release-* branch when building releases, so we don't have a way to set the SemVer versions on the command-line API that the removed document depends on. We will attempt to preserve any command-line API that occurs in official documentation, but we can no longer make formal SemVer statements about breaking compat.
I'd added these in 28592d0 (docs/user/versioning: Document APIs covered by our Semantic Versioning, 2018-12-17, openshift#935). But v0.16.1 was the last installer release. Since then, OpenShift tooling picks whatever the most recent commit is in the appropriate release-* branch when building releases, so we don't have a way to set the SemVer versions on the command-line API that the removed document depends on. We will attempt to preserve any command-line API that occurs in official documentation, but we can no longer make formal SemVer statements about breaking compat.
Also roll the tips-and-tricks docs into the overview's multi-invocation docs, since they'd been covering the same ground with slightly different wording before. I've expanded the unified description to go into a bit more detail and tie in the new versioning docs.
I've also documented the
manifest-templatestarget from 166a9f1 (#592).CC @smarterclayton, @derekwaynecarr, @eparis.