sending podman 2.x major version bump to next stream first
#560
Comments
|
IMO this PR really should get merged containers/podman#6842 and baked into a release first and podman 2.0.2 has a lot of fixes that maybe are worth waiting for. |
|
We discussed this in the meeting today. |
dustymabe
added a commit
to dustymabe/fedora-coreos-config
that referenced
this issue
Jul 9, 2020
Pin podman major version for now while we let the next major version soak in the `next` stream. coreos/fedora-coreos-tracker#560
dustymabe
added a commit
to dustymabe/fedora-coreos-pipeline
that referenced
this issue
Jul 9, 2020
We want to experiment in `next` with the major podman version bump so let's re-enable `next-devel`. See coreos/fedora-coreos-tracker#560 This reverts commit d65ae1c.
dustymabe
added a commit
to dustymabe/fedora-coreos-config
that referenced
this issue
Jul 9, 2020
Pin podman major version for now while we let the next major version soak in the `next` stream. Closes coreos/fedora-coreos-tracker#560
dustymabe
added a commit
to coreos/fedora-coreos-pipeline
that referenced
this issue
Jul 9, 2020
We want to experiment in `next` with the major podman version bump so let's re-enable `next-devel`. See coreos/fedora-coreos-tracker#560 This reverts commit d65ae1c.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
podman-2.0.1-1.fc32landed in fedora stable (and thus FCOStesting-devel) last week. Since this is a major version bump should we consider letting this soak innextfor a cycle before sending it totesting?The text was updated successfully, but these errors were encountered: