Fedora CoreOS APAC community members want to make sure in advance that we
enough community members to attend regular CoreOS APAC meeting so that we
some fruitful discussion. This will help us to plan ahead whether we want to
keep or cancel next meeting depending upon availability.
We expect at least 3 community members to be present to keep next meeting,
not we will cancel it.
Meeting Calendar - https://apps.fedoraproject.org/calendar/CoreOS/#m9313
(bi-weekly meeting on every alternate Tuesday, 5:00 UTC at
#fedora-meeting-1 on freenode)
We will use this etherpad as reference (until we have better option) for
Please add your name on or before 16:00 UTC(21:30 PM IST) Monday
(the day before we have our next meeting) to help us decide next meeting
For example: If next Fedora CoreOS APAC meeting is on 27th November
5:00 UTC then please add you availability during meeting on or before 26th
November(Monday), 16:00 UTC
Thanks for your co-operation!
It is now possible to use bodhi to release a new container build. Currently
it is following the same flow as packages.
After a successful OSBS build, a bodhi update can be created. Fedpkg does
not yet support creating updates for containers , so you have to either
use bodhi web UI or the bodhi cli. For example
bodhi updates new --type enhancement --notes "cockpit update to version
Once the update is pushed to testing, the container will be available in
the registry with the testing tag
podman pull registry.fedoraproject.org/f29/cockpit:testing
Then the container latest tag will be pushed to registry.fedoraproject.org,
if it receives +3 karma or waits 7 days in testing.
 - https://pagure.io/fedpkg/issue/296