15:00:00 #startmeeting Bodhi stakeholders (2017-10-10) 15:00:00 Meeting started Tue Oct 10 15:00:00 2017 UTC. The chair is bowlofeggs. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:00 The meeting name has been set to 'bodhi_stakeholders_(2017-10-10)' 15:00:00 #meetingname bodhi_stakeholders 15:00:00 #topic salutations 15:00:00 The meeting name has been set to 'bodhi_stakeholders' 15:00:00 #chair bowlofeggs caleigh dgilmore masta mboddu nirik pbrobinson puiterwijk Kellin jcline 15:00:00 Current chairs: Kellin bowlofeggs caleigh dgilmore jcline masta mboddu nirik pbrobinson puiterwijk 15:01:12 howdy 15:03:37 might just be us today masta 15:04:05 looks that way 15:04:06 Well, hi. 15:04:14 3 now ☺ 15:04:56 well it'll probably be a short and sweet meeting today then 15:05:10 #topic announcements and information 15:05:11 #info Bodhi 2.11.0 is deployed to production, with a new update batching feature. Tuesday releases will include batched updates. 15:05:11 #info A Bodhi 2.12.0 release is planned to be deployed ASAP 15:05:26 #info 2.12.0 is planned to have these changes: https://github.com/fedora-infra/bodhi/pull/1879/files 15:06:00 i'm working on building a 2.12.0 beta to test on stg. if it goes well, i hope to deploy to prod when there's a window 15:06:22 #info A 2.13.0 is also planned to be deployed, hopefully before the freeze, with modular mashing 15:06:46 #info all other bodhi changes on develop will unfortunately wait for a 2.14.0, after freeze 15:07:14 the goal of these releases is to a) make them very small diff-wise, so that b) they can be rolled back easily if there are problems 15:07:28 neither of them have migrations, so a dnf downgrade should suffice 15:07:37 questions/thoughts? 15:08:55 was just reading the links 15:09:22 the atomic pipeline stuff looks good 15:09:44 yeah i hope it works well 15:09:59 it's not easy to test it because there's not much data yet 15:10:13 and i think we need a corresponding fix to be deployed in the pipeline before data will appear 15:10:21 so i'm taking that PR on faith 15:10:47 (i don't think it will break anything if the data isn't tehre, it'll just no-op) 15:10:50 if it doesn't work, then we can fix it. 15:10:54 yeah 15:11:25 since it's JS it also won't interfere with the server's operation 15:11:52 i don't have any other topics for this month, so we can open floor 15:11:56 #topic Open floor 15:12:37 oh i guess there was one other large announcement i forgot 15:12:59 #info Bodhi no longer supports EL 7, starting with 2.12.0 15:13:12 #undo 15:13:12 Removing item from minutes: INFO by bowlofeggs at 15:12:59 : Bodhi no longer supports EL 7, starting with 2.12.0 15:13:15 #info Bodhi no longer supports EL 7, starting with 2.11.0 15:13:19 why is that? 15:13:34 bodhi needs a version of pungi that is only available on F25+ 15:13:48 fair enough 15:13:49 that was just the straw that broke the camel's back though 15:14:04 it has been difficult for me to keep bodhi building/working on EL 7 for some time 15:14:19 EL 7 formally ships a version of WebOb that is too old for EPEL 7's Pyramid 15:14:28 yeah, understandable 15:14:30 and so someone packaged a python-webob1.4 package 15:14:52 but you have to do reaaaaallly crazy stuff to get python processes to use the python-webob1.4 package instead of the python-webob package 15:15:02 and it breaks often when i update, and it costs me a lot of time 15:15:23 so those two things together motivated me to choose to only support Fedora 15:15:42 so puiterwijk kindly upgraded all production bodhi servers to F25 for me (backend01 was already F25) 15:16:00 So when we do maintenance on bodhi, it seems to cause packages to get in limbo... claiming they are not signed (but they are signed) 15:16:05 and we'll probably just stick to odd-numbered Fedoras in prod, so we'll update to F27 when it is released 15:16:30 masta: yeah, if bodhi is offline when signing happens it can miss fedmsgs about that 15:17:11 any thoughts how the situation could improve? 15:17:11 masta: puiterwijk wrote me a PR to make bodhi-push recover from that some time ago, but it needs tests. i have a todo to write the tests for it, but i just have been swamped with all the modularity and CI stuff 15:17:48 basically, the idea is that bodhi-push should notice unsigned builds and double check that we didn't just miss messages. if they turn out to be signed, just mark them signed and continue. should work much better 15:18:01 it's def on my todo list, just not at the top ☹ 15:18:32 okay, cool. 15:18:59 apologies for the rough ride 15:19:16 it might stay rough for the next while too, since so many crazy changes are happening 15:19:21 it's a lot to keep up with 15:19:37 that's why i'm trying to make these next releases as small as possible 15:19:43 hopefully it'll help wtih stability 15:19:52 better to have smaller, more frequent, releases 15:20:21 yeah to some extent, though making releases also costs time and the size of the release doesn't affect the time that much 15:20:29 so you know, like daily releases would be a bad idea ☺ 15:20:45 i usually do a release for each of these meetings, so ~once every 4 weeks 15:21:01 i think that's been a nice cadence, though right now is an anomaly 15:21:36 anything else, or shall we end? 15:22:31 nothing, let's wrap 15:22:34 #endmeeting