21:01:17 #startmeeting swift 21:01:18 Meeting started Wed Dec 19 21:01:17 2018 UTC and is due to finish in 60 minutes. The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:01:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:01:21 The meeting name has been set to 'swift' 21:01:28 who's here for the swift team meeting? 21:01:30 o/ 21:01:32 hi 21:01:55 o/ 21:02:26 welcome 21:02:39 not sure who else will be here. there's a few people I know are out today 21:02:58 today i wanted to talk about the 2.20.0 release 21:03:02 first up, it's done! 21:03:07 \o/ 21:03:14 yey! 21:03:29 congrats! 21:03:33 thanks for your work on it 21:03:58 the superuser people asked me to write up a short blog post on it. it's published at http://superuser.openstack.org/articles/a-birds-eye-view-of-swift-2-20-0/ 21:04:14 nice 21:04:24 #link http://superuser.openstack.org/articles/a-birds-eye-view-of-swift-2-20-0/ 21:04:36 ^for the people reading meeting minutes later ;) 21:04:40 heh 21:04:49 the 2.19 -> 2.20 gap was pretty large (four months), and there were a lot of good changes 21:05:07 the s3 compatibility stuff definitely unblocks a lot of future s3 compat work. 21:05:21 I know swiftstack will be looking at versioning soon 21:05:33 nice 21:05:46 timburke: kota_: mattoliverau: any comments about the release? anythign that went well or poorly? 21:05:52 and i can finally switch people from using (my hacked up) swift3! 21:06:06 +1 21:06:12 ^ I was just about to ask timburke if it was enough for that. 21:06:13 +1 21:06:21 so great! 21:07:03 I have a slight preference for not waiting 4 months until the next release, but I don't feel like we missed any opportunities by not releasing earlier 21:07:23 as a reminder, here's the openstack stein schedule: 21:07:25 #link https://releases.openstack.org/stein/schedule.html 21:07:52 the important thing is the april deadline for a release 21:08:09 I don't know if we'll have one before then or not, but we definitely will have a release that week (or slightly before) 21:08:41 yeah, given the final release deadline of Apr 1-5, we'd better not wait four months for the next one ;-) 21:08:51 kk, and maybe a swift client release around march would be good too, if I read that right 21:09:04 mattoliverau: oh. right. swiftclient. 21:09:05 +1 21:09:13 well that's when they want to freeze 21:09:16 :-) 21:09:27 oh, right. I want to also tag some stable releases as well 21:09:31 Mar 4-8: Final release for client libraries 21:09:39 we've got some backports to land 21:09:48 and by "we" I know it means me ;-) 21:10:02 but any +1s there makes it easier for me to quickly land them 21:10:05 lol 21:10:35 you know notmyname, you *can* delegate authority ;-) 21:10:48 I used to run some stable saio intances, maybe I should do that thing again. it made testing backports easier 21:10:49 timburke: in this case, I'm not actually sure if I can. perhaps 21:11:07 mattoliverau: we've got the experimental jobs that look good 21:11:11 need to talk to stable team 21:11:15 TBH, I probably won't look at them until january. I'm only in the office today and tomorrow, then I'll be off until jan 2 21:11:34 oh yeah, btw timburke awesome work on testing jobs and awesomeness. 21:11:53 I don't think our stable branch policy and reviews is something that needs a lot of changes right now 21:12:16 yeah, the new zuul tests are great and made me a lot more confident in this release 21:12:17 eh? oh, the busted jobs...? 21:12:25 not any more! 21:12:47 tdasilva is the one to thank for the rolling upgrade, though :-) make me feel much better 21:13:06 +1 21:13:17 looking ahead, py3 is a looming thing. zaitcev is working hard on it. canonical stopped by to ask for it. mattoliverau needs it for suse 21:13:47 account server should be good! hopefully 21:13:56 the "real" deadline is basically 12 months from now. the openstack deadline is the end of the T release. however, all the distros are cutting some sort of LTS before then, so that's what they're tracking 21:14:07 🤞 21:14:10 yeah, I saw this morning that landed. nice 21:14:11 yeah 21:14:49 how hopeful are we that we can do it by stein? 21:15:00 how much will it hurt if we don't? 21:15:30 timburke: I think if we don't, swift may not be included in "openstack" by some distros 21:15:50 might be the sort of questions for which it'd be nice to have zaitcev :-) 21:16:02 good point. gotta hurt a bit 21:16:34 tbh the whole latin-1/ascii for wsgi and utf8 encoded breaks my head. Oh zaitcev responded in the patch.. I shall read it and hopfully some balls will drop. 21:17:12 it's icky, and unfortunate. i can talk after the meeting about it if you want 21:18:10 I think I've said everythign that I was wanting to say about the release and what's likely coming in january 21:18:16 kota_: mattoliverau: timburke: anything else to bring up or to add? 21:18:39 kota_: you and tdasilva and rledisez will be at FOSDEM next month. I hope you all have a great time 21:18:50 timburke: sure, though I'll probably forget over the Christmas holidays :P I'll read what zaitcev wrote and then get back to you. maybe in the new year :P last week for me too. 21:18:52 mattoliverau and I will be at LCA at about the same time 21:19:12 dunno if anyone else has seen IOErrors popping out of eventlet, but i wrote up https://github.com/eventlet/eventlet/pull/532 to fix some i saw 21:19:17 notmyname: I'm planning it. I'm looking forward to making it :) 21:19:54 timburke: you should come to LCA ;) then we can have 3 at each! 21:20:10 lol 21:20:20 might be a little late to buy travel ;-) 21:21:11 anything else from anyone? 21:21:40 all right, then 21:21:46 reminder that there is no meeting next week 21:22:21 next meeting is jan 2, and I expect us to pretty much just talk about this same stuff, to remind ourselves what we forgot :-) 21:22:32 have a good christmas week and a new year! 21:22:59 thanks. and same to everyone else :-) 21:23:04 thanks for your work on swift 21:23:14 #endmeeting