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

[v3.0.1] set version to v3.0.1 #10515

Merged
merged 1 commit into from Jun 1, 2021

Conversation

vrothberg
Copy link
Member

The v3.0.1 branch included the bump to v3.0.2-dev which indicates the
state in between two releases.

Fixes: bugzilla.redhat.com/show_bug.cgi?id=1966538
Signed-off-by: Valentin Rothberg rothberg@redhat.com

The v3.0.1 branch included the bump to v3.0.2-dev which indicates the
state in between two releases.

Fixes: bugzilla.redhat.com/show_bug.cgi?id=1966538
Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 1, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vrothberg

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 1, 2021
@vrothberg
Copy link
Member Author

/hold
Not yet acked.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 1, 2021
@mheon
Copy link
Member

mheon commented Jun 1, 2021

I wonder if this would cause any RPM issues - is the package that went out tagged as 3.0.2, not 3.0.1? If so we probably need to bump to 3.0.2 here to avoid a situation where we've "downgraded" the RHEL package.

@vrothberg
Copy link
Member Author

I wonder if this would cause any RPM issues - is the package that went out tagged as 3.0.2, not 3.0.1? If so we probably need to bump to 3.0.2 here to avoid a situation where we've "downgraded" the RHEL package.

The package is podman-3.0.1-6.module+el8.4.0+10607+f4da7515.ppc64le, so I think we're good.

@mheon
Copy link
Member

mheon commented Jun 1, 2021

OK, good.

@rhatdan
Copy link
Member

rhatdan commented Jun 1, 2021

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 1, 2021
@TomSweeneyRedHat
Copy link
Member

LGTM
@mheon @rhatdan, OK to cancel the hold on this? Green buttons everywhere.

@TomSweeneyRedHat
Copy link
Member

@rhatdan
Copy link
Member

rhatdan commented Jun 1, 2021

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 1, 2021
@openshift-merge-robot openshift-merge-robot merged commit 4d61a03 into containers:v3.0.1-rhel Jun 1, 2021
@vrothberg vrothberg deleted the bz-1966538 branch June 2, 2021 06:23
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants