12:44:31 <toabctl> #startmeeting rpm_packaging
12:44:31 <openstack> Meeting started Wed Jun 19 12:44:31 2019 UTC and is due to finish in 60 minutes.  The chair is toabctl. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:44:32 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:44:34 <openstack> The meeting name has been set to 'rpm_packaging'
12:44:37 <toabctl> sorry for being late
12:45:13 <toabctl> ping toabctl, dirk, apevec, jpena, jruzicka, number80, kaslcrof, cmurphy
12:45:23 <toabctl> #chair jpena dirk cmurphy toabctl
12:45:23 <openstack> Current chairs: cmurphy dirk jpena toabctl
12:49:03 <jpena> dirk: so back to the topic. If we want to remove python2 before the end of the cycle, we could just remove the centos-based job, and keep just the Fedora one. Then, once centos 8 is out, we'd add the new job and ideally remove the fedora one
12:53:55 <dirk> is that okay for you?
12:54:00 <dirk> would work for me
12:55:18 <jpena> yes, we can do it
12:55:56 <jpena> #action jpena to disable the centos7-based job for master, keep only fedora until centos8 is available
13:01:02 <dirk> thanks
13:01:38 <dirk> I guess removing python2 has a lot of other implications
13:02:44 <dirk> however I think removing it helps us in aligning a bit more (don't need singlespec anymore and we can drop python 2.x specific stuff from the build environments, which are currently quite large due to that)
13:06:56 <toabctl> we still need somebody who does convert the services to py3..
13:09:40 <dirk> some are already converted
13:10:01 <dirk> I hope to be able to allocate some workforce from SUSE on this within the next few days
13:10:14 <toabctl> yes. but I wonder if anybody every used theses services.
13:14:41 <dirk> we never implemented a ci using them
13:14:56 <dirk> at some point we pointed openstack-ansible to it, but then realized that the services don't work
13:15:07 <toabctl> I'm currently trying to use them with our internal quickstart tool
13:15:14 <toabctl> ah. ok
13:17:43 <dirk> yep, that could also be tried
13:18:11 <dirk> capture that as an action item?
13:18:30 <dirk> another thing that I'm wondering is if we want to switch to a bot proposing updates when new versions are released
13:19:03 <toabctl> +1 for the bot.
13:23:53 <toabctl> #action toabctl try to use openstack-quickstart with upstream packages
13:23:57 <toabctl> anything else?
13:25:50 <toabctl> #endmeeting