I don't know the formal process for proposal but here is a shot at a bare minimum
start for trying to add containers to the existing release criteria. This is a suggestion
after we found podman can't pull containers from a registry in f31 .
New section for Containers and Container tools:
- A Fedora system can install the podman container runtime
- The podman container runtime can pull/run a container from Fedora's registry as root
- The podman container runtime can pull/run a container from Fedora's registry as a non-root user
As for the container I'd suggest the previous fedora release's container (i.e. f30 for f31).
I got feedback from Adam and Ben today; so the following changes have
I have added a little paragraph at the beginning to say what a last
minute blocker bug is. I used freeze as the time anchor rather than a
meeting since that seems to be the most firm time constraint we work to.
Perhaps the review meetings could be anchored to the freeze as well.
There might be some merit to showing the critical meetings in the
schedule list that gets published.
I changed "team" to "stakeholder groups"
I removed "proposed" from places where it really didn't add anything.
Have a Great Day!
building a new dev box, don't care about the rough edges so want to
install whatever will eventually allow me to upgrade to fedora 31 ...
downloaded Fedora-Workstation-Live-x86_64-Rawhide-20190816.n.0.iso and
installed only to notice it's pre-release fedora 32, checked the
release schedule and, sure enough, the fedora 31 branch happened
earlier this month so this image is already rawhide for fedora 32.
what is the *proper* ISO to install that will eventually get me to
fedora 31? thanks.
Robert P. J. Day Ottawa, Ontario, CANADA
Just started to test F31. The Xfce and KDE spins are going OK. I'm using VirtualBox-6.0-6.0.10 directly from Oracle on the host.
Fedora-Workstation-Live-x86_64-31-20190828.n.0.iso boots fine and the Install to boot completes without error.
However, when booting to the installed system I get the screen:
Oh no! Something has gone wrong
A problem has occurred and the system can't recover.
Is this a known issue? I'm guessing it has to do with an Wayland issue and the VBox Video drivers. However, I don't know how to prove that.
If simple questions can be answered with a simple google query then why are there so many of them?