18:02:04 <syeghiay> #startmeeting F27 Releng Retrospective
18:02:04 <zodbot> Meeting started Mon Dec  4 18:02:04 2017 UTC.  The chair is syeghiay. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:02:04 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:02:04 <zodbot> The meeting name has been set to 'f27_releng_retrospective'
18:02:11 <sgallagh> o/
18:02:31 <zodbot> dgilmore: Error: Can't start another meeting, one is in progress.
18:02:43 <dgilmore> https://public.etherpad-mozilla.org/p/FedoraRelease27RelEngRetrospective
18:02:58 <bowlofeggs> .hello2
18:03:01 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <randy@electronsweatshop.com>
18:03:01 <mattdm> #link https://meet.jit.si/fedora27retro
18:03:05 <mattdm> ^ live participation
18:03:09 <tflink> .hello tflink
18:03:11 * threebean waves
18:03:11 <zodbot> tflink: tflink 'Tim Flink' <tflink@redhat.com>
18:03:16 <dustymabe> i like the puiterbot
18:03:26 <syeghiay> dgilmore: I already started the meeting. ;-)
18:03:38 <dgilmore> syeghiay: here?
18:03:46 <dgilmore> gahh I missed
18:03:52 <dgilmore> syeghiay: I failed :D
18:04:43 <mattdm> #link https://www.youtube.com/c/MatthewMiller-mattdm/live
18:04:56 <mattdm> #info live stream (slightly delayed)
18:05:57 <puiterwijk> There's not a lot that went well seemingly?
18:12:08 <dustymabe> puiterwijk: considering we released the beast and we have got a lot of good reviews
18:12:14 <dustymabe> that is certainly an accomplishment
18:12:36 <puiterwijk> dustymabe: yeah, sorry, that was a remark when Kate was asking for good things and nobody entered anything :)
18:12:47 <dustymabe> :)
18:20:55 <bowlofeggs> sgallagh: it might help for me to clarify what i meant about lead time
18:21:15 <bowlofeggs> sgallagh: imo, it would have been better for there to have been an f26 modular spin
18:21:39 <bowlofeggs> sgallagh: and, in particular, i would have liked to know i needed to make bodhi support modularity earlier than june
18:22:16 <dustymabe> bowlofeggs: didn't we have some sort of modular thing we released with f26 ?
18:22:52 <bowlofeggs> dustymabe: there was the boltron thing, but it wasn't a spin
18:23:05 <dustymabe> k
18:23:07 <bowlofeggs> dgilmore: yeah, agreed - like a spin
18:26:14 <bowlofeggs> i agree with threebean  :)
18:26:27 <puiterwijk> I think part of the bodhi+pungi stuff is related somewhat to modularity/factory2.0
18:26:38 <threebean> bowlofeggs++
18:26:38 <zodbot> threebean: Karma for bowlofeggs changed to 8 (for the f27 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
18:27:01 <bowlofeggs> threebean++ :)
18:27:01 <zodbot> bowlofeggs: Karma for ralph changed to 1 (for the f27 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
18:27:23 <puiterwijk> threebean++ bowlofeggs++
18:27:23 <zodbot> puiterwijk: Karma for ralph changed to 2 (for the f27 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
18:27:29 <threebean> puiterwijk++ karma party!
18:33:31 <dustymabe> puiterwijk++
18:37:54 <jwf> I think that was katec, but I use the Community Blog to keep up with things that are happening. I try to use that to keep tabs on what's happening, both technical and non-technical topics…
18:38:23 * jwf is learning more about the past release cycle from watching this stream than following along on mailing lists / IRC for the last few months
18:38:26 <jwf> Or at least, from this angle.
18:39:09 <bowlofeggs> i think i missed a few minutes due to wifi issues
18:42:02 <syeghiay> #action Schedule Slipping: investigate how to cope with such a short release cycle and if we still think skipping alpha is still worth the benefits
18:43:24 <bowlofeggs> i think people can't hear me
18:43:28 <bowlofeggs> but i wrote this stuff
18:48:26 <syeghiay> #action Process Needed: investigate how we can ensure rel-eng is keep in loop regarding important items
18:50:32 <dustymabe> threebean: don't get me wrong. I think having dist-git on pagure is awesome! I've wanted pull request based git for dist-git for a long time!
18:50:42 <threebean> :p
18:50:49 <bowlofeggs> dgilmore: is it the registry, or the build system?
18:50:56 <dustymabe> regardless of atomic host testing or modularity I think it's still a win, but would be good to close the gaps on features that are missing
18:51:20 <bowlofeggs> dgilmore: afaik, it's the build system that doesn't make the images
18:51:25 <bowlofeggs> OSBS i mean
18:51:46 <dustymabe> bowlofeggs: koji makes those images using kickstart I think
18:51:52 <syeghiay> #action Packager Tooling not feature complete: investigate how we can repair this moving forward
18:52:10 <puiterwijk> No, our OSBS does not do multi-arch
18:52:15 <puiterwijk> Our registry could, but we don't upload it
18:52:37 <puiterwijk> Adam was working on multi-arch OSBS, but that hasn't finished yet.
18:52:59 <puiterwijk> mboddu: ^
18:53:16 <bowlofeggs> yeah i think it is OSBS
18:53:23 <mboddu> puiterwijk: Oh, I thought its done. Thanks
18:53:25 <bowlofeggs> the registry is just docker-distribution, which should support it
18:53:39 <bowlofeggs> i still can't seem to speak in the meeting
18:53:48 <puiterwijk> bowlofeggs: well, sort of. We also don't push the other arches to our main registry. Which is really simple to fix. But it hasn't been done yet
18:54:27 <puiterwijk> dgilmore: the regsitry has the support.
18:54:32 <puiterwijk> But we just haven't pushed them yet
18:54:33 <bowlofeggs> oh so we do build the images
18:54:42 <dustymabe> bowlofeggs: yes
18:54:42 <bowlofeggs> and we just need to make "something" push them there?
18:54:43 <puiterwijk> Yes. We just don't have the SOP to push stuff
18:54:45 <bowlofeggs> cool
18:54:46 <dgilmore> puiterwijk: okay :D
18:55:15 <puiterwijk> dgilmore: I can see if I can fix that this week
18:55:26 <dgilmore> puiterwijk: okay :D
18:55:50 <mboddu> puiterwijk++
18:56:59 <dustymabe> let's still please open an issue and track the work
18:58:40 <syeghiay> #action Multiarch Support in container registry: investigate how we can better communicate/collaborate on the multi arch efforts - central point for this type of communication?
18:59:07 <syeghiay> #action Multiarch Support in container registry: create issue for this problem
18:59:24 <dustymabe> dgilmore: we can hear kate fine
18:59:28 <dustymabe> dgilmore: are you still with us
18:59:42 <dgilmore> dustymabe: I am hearing nothing
18:59:43 <syeghiay> dgilmore: we can hear you
18:59:45 <mboddu> dgilmore: We can hear you but you cant
19:00:26 <dgilmore> I can hear after reconnecting
19:00:41 <syeghiay> #action Addition of s390 architecture: investigate process for change management
19:00:57 <syeghiay> #action Addition of s390 architecture: investigate process for portfolio (multi-project) management
19:01:18 <bowlofeggs> thanks!
19:01:24 <syeghiay> #action Lack of project management: investigate establishing more project management processes
19:02:10 <jwf> katec++
19:02:10 <zodbot> jwf: Karma for katec changed to 2 (for the f27 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
19:02:17 <dustymabe> katec++
19:02:17 <zodbot> dustymabe: Karma for katec changed to 3 (for the f27 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
19:02:25 * dgilmore goes to get changed nwo
19:02:27 <dgilmore> now
19:02:42 <dgilmore> katec++
19:02:42 <zodbot> dgilmore: Karma for katec changed to 4 (for the f27 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
19:02:46 <dgilmore> syeghiay++
19:02:46 <zodbot> dgilmore: Karma for syeghiay changed to 1 (for the f27 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
19:02:57 <syeghiay> #endmeeting thanks all