Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-1/2018-11-28/fedora_coreos…
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-1/2018-11-28/fedora_coreos…
Log:
https://meetbot.fedoraproject.org/fedora-meeting-1/2018-11-28/fedora_coreos…
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by bgilbert at 16:30:01 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2018-11-28/fedora_coreos…
.
Meeting summary
---------------
* roll call (bgilbert, 16:30:05)
* Action items from last meeting (bgilbert, 16:34:01)
* dustymabe added questions about versioning/patch release to #81
(dustymabe, 16:35:06)
* Throttled update rollouts (bgilbert, 16:35:37)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/83
(bgilbert, 16:35:44)
* LINK: https://github.com/coreos/fero (bgilbert, 16:42:54)
* LINK: https://pagure.io/robosignatory (dustymabe, 16:44:15)
* ACTION: dustymabe to set up conversation with Patrick and Kevin
about release signing (bgilbert, 16:45:28)
* ACTION: dustymabe to write up a ticket on release signing
(bgilbert, 16:45:39)
* Collect metrics from Fedora CoreOS machines (bgilbert, 16:52:47)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/86
(bgilbert, 16:52:55)
* Version numbering for OS releases (bgilbert, 17:04:11)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/81
(bgilbert, 17:04:16)
* Open Floor (bgilbert, 17:23:16)
* we've been in heavy development on the fedora-coreos-pipeline (new
repo recently moved under the coreos github org) (dustymabe,
17:24:17)
* LINK: https://github.com/coreos/fedora-coreos-pipeline (dustymabe,
17:24:37)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/37
(leoluk, 17:29:16)
* ACTION: jbrooks to create a ticket for deciding on the mechanism for
shipping kube/okd pieces (bgilbert, 17:33:39)
* ACTION: jlebon to file a ticket to decide whether we need modularity
support in rpm-ostree (bgilbert, 17:34:54)
Meeting ended at 17:38:07 UTC.
Action Items
------------
* dustymabe to set up conversation with Patrick and Kevin about release
signing
* dustymabe to write up a ticket on release signing
* jbrooks to create a ticket for deciding on the mechanism for shipping
kube/okd pieces
* jlebon to file a ticket to decide whether we need modularity support
in rpm-ostree
Action Items, by person
-----------------------
* dustymabe
* dustymabe to set up conversation with Patrick and Kevin about
release signing
* dustymabe to write up a ticket on release signing
* jbrooks
* jbrooks to create a ticket for deciding on the mechanism for
shipping kube/okd pieces
* jlebon
* jlebon to file a ticket to decide whether we need modularity support
in rpm-ostree
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* bgilbert (94)
* dustymabe (74)
* zodbot (31)
* jlebon (27)
* slowrie (14)
* ajeddeloh (11)
* ksinny (9)
* leoluk (6)
* kaeso (6)
* rfairley (5)
* jbrooks (5)
* x3mboy (5)
* jligon (3)
* miabbott (2)
* mnguyen_ (2)
* sayan (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Hi,
Fedora CoreOS APAC community members want to make sure in advance that we
have
enough community members to attend regular CoreOS APAC meeting so that we
have
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,
if
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[1] as reference (until we have better option) for
future
meetings.
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
plan.
For example: If next Fedora CoreOS APAC meeting is on 27th November
(Tuesday),
5:00 UTC then please add you availability during meeting on or before 26th
November(Monday), 16:00 UTC
Thanks for your co-operation!
[1] https://public.etherpad-mozilla.org/p/Fedora_CoreOS_APAC_meeting
Dear all,
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 [0], 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
181-2" cockpit-181-2.fc29
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.
Thanks
[0] - https://pagure.io/fedpkg/issue/296