Skip to content
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

Add krel stage/release entry methods #1682

Merged
merged 1 commit into from
Nov 4, 2020
Merged

Add krel stage/release entry methods #1682

merged 1 commit into from
Nov 4, 2020

Conversation

saschagrunert
Copy link
Member

@saschagrunert saschagrunert commented Nov 4, 2020

What type of PR is this?

/kind feature

What this PR does / why we need it:

This cleans-up the previous anago part within the release package as
well as the anago subcommand.

We now define a new Stage/Release API inside of pkg/anago, which
will be later on used by the krel stage/release subcommands.

Which issue(s) this PR fixes:

Refers to #1673

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

None

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/feature Categorizes issue or PR as related to a new feature. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. area/release-eng Issues or PRs related to the Release Engineering subproject and removed needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Nov 4, 2020
@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 4, 2020
This cleans-up the previous anago part within the release package as
well as the anago subcommand.

We now define a new `Stage`/`Release` API inside of `pkg/anago`, which
will be later on used by the `krel stage/release` subcommands.

Signed-off-by: Sascha Grunert <sgrunert@suse.com>
@saschagrunert
Copy link
Member Author

This is ready for review. After that we can move over the first logical bits from krel anago … subcommands into the new (empty) methods. This also means that we can populate the StageOptions and ReleaseOptions.

@justaugustus
Copy link
Member

It's really happening now!
/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 4, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justaugustus, saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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

@k8s-ci-robot k8s-ci-robot merged commit d0adf92 into kubernetes:master Nov 4, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.20 milestone Nov 4, 2020
@saschagrunert saschagrunert deleted the krel-stage-release-entry branch November 5, 2020 08:18
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. area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority release-note-none Denotes a PR that doesn't merit a release note. sig/release Categorizes an issue or PR as relevant to SIG Release. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants