Skip to content

Conversation

@wking
Copy link
Member

@wking wking commented Dec 18, 2018

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 (#592).

CC @smarterclayton, @derekwaynecarr, @eparis.

@openshift-ci-robot openshift-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Dec 18, 2018
Copy link
Member Author

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.

@abhinavdahiya
Copy link
Contributor

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.

^^ @crawford

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 21, 2018
@crawford
Copy link
Contributor

crawford commented Jan 4, 2019

Can you rebase this so we can get this in?

@wking
Copy link
Member Author

wking commented Jan 4, 2019

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).
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 4, 2019
@wking
Copy link
Member Author

wking commented Jan 4, 2019

Prow seemed hung ("shellcheck Expected — Waiting for status to be reported" and similar), so I've pushed 8df754a -> 28592d0 with a new commit date.

@crawford
Copy link
Contributor

crawford commented Jan 5, 2019

/approve

@wking
Copy link
Member Author

wking commented Jan 5, 2019

/retest

@wking
Copy link
Member Author

wking commented Jan 5, 2019

Finally all green :).

@crawford
Copy link
Contributor

crawford commented Jan 5, 2019

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 5, 2019
@openshift-ci-robot
Copy link
Contributor

[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

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit eb781ff into openshift:master Jan 5, 2019
@wking wking deleted the api-stability branch January 5, 2019 23:00
wking added a commit to wking/openshift-installer that referenced this pull request Jan 5, 2019
Through eb781ff (Merge pull request openshift#935 from wking/api-stability,
2019-01-04).
wking added a commit to wking/openshift-installer that referenced this pull request Oct 1, 2019
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.
jhixson74 pushed a commit to jhixson74/installer that referenced this pull request Dec 6, 2019
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants