(Announcing the Change proposal) |
|||
| Line 17: | Line 17: | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeReadyForFesco]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
| Line 36: | Line 36: | ||
--> | --> | ||
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/4JRMF5IWBYZIOWG2UB2YVGXBWAQ36NMZ/ devel thread] | * [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/4JRMF5IWBYZIOWG2UB2YVGXBWAQ36NMZ/ devel thread] | ||
* FESCo issue: | * FESCo issue: [https://pagure.io/fesco/issue/2749 #2749] | ||
* Tracker bug: <will be assigned by the Wrangler> | * Tracker bug: <will be assigned by the Wrangler> | ||
* Release notes tracker: <will be assigned by the Wrangler> | * Release notes tracker: <will be assigned by the Wrangler> | ||
Revision as of 14:31, 1 February 2022
Podman 4.0
Summary
Podman 4.0 will be released in Fedora 36 for the first time.
Owner
- Name: Dan Walsh
- Email: dwalsh@fedoraproject.org
Current status
- Targeted release: Fedora Linux 36
- Last updated: 2022-02-01
- devel thread
- FESCo issue: #2749
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
Podman 4.0 will be fully released for the first time in Fedora 36. The API has had breaking changes so it will not be released to stable in Fedora 34 or Fedora 35. Podman 4.0 has a huge amount of changes and a brand new network stack.
Feedback
Benefit to Fedora
Podman 4.0 has a huge list of new features, highlighted by a brand new network stack. Lots of improvements and bug fixes.
See more here: https://github.com/containers/podman/releases/tag/v4.0.0-rc2
Scope
- Proposal owners:
It is in RC2, now, so just complete the release.
- Other developers:
N/A
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
Podman 3.* release will not be able to connect to Podman 4.0 via remote API, similarly Podman 4.0 will not be able to connect to Podman 3.* API.
Existing network stack will continue to run, on existing systems. All containers and images need to be removed to try out the new network stack.
How To Test
Just test on existing systems. All Podman containers and images should continue to work. And all compatibility API (docker-compose, docker.py) should continue to work.
User Experience
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)