Thursday, 2019-06-27

*** openstack has joined #openstack-release13:12
*** ChanServ sets mode: +o openstack13:12
*** bobh has joined #openstack-release13:20
openstackgerritJean-Philippe Evrard proposed openstack/releases master: Release OpenStack-Ansible Stein  https://review.opendev.org/66672813:21
*** bobh has quit IRC13:22
*** hberaud has joined #openstack-release13:25
*** hberaud has left #openstack-release13:34
*** dave-mccowan has quit IRC13:43
*** pcaruana has quit IRC13:46
*** pcaruana has joined #openstack-release13:47
*** mtreinish has joined #openstack-release13:56
*** ykarel|afk is now known as ykarel14:02
*** mlavalle has joined #openstack-release14:15
*** bobh has joined #openstack-release14:16
openstackgerritEric Fried proposed openstack/releases master: Release os-traits 0.15.0  https://review.opendev.org/66711114:21
*** ykarel is now known as ykarel|away14:46
*** pcaruana has quit IRC15:14
*** udesale has joined #openstack-release15:25
openstackgerritDmitry Tantsur proposed openstack/releases master: Release python-ironic-inspector-client 3.6.1 for Train  https://review.opendev.org/66796415:32
smcginnisShould this be retired? https://opendev.org/openstack/release-schedule-generator15:56
*** e0ne has quit IRC16:02
*** hberaud has joined #openstack-release16:05
*** bobh has quit IRC16:06
*** jpich has quit IRC16:20
*** amoralej is now known as amoralej|off16:27
*** whoami-rajat has quit IRC16:44
*** udesale has quit IRC16:54
*** whoami-rajat has joined #openstack-release17:06
dhellmannsmcginnis : probably? we have the thing in the releases repo now and the data in that repo looks obsolete17:10
smcginnisYeah, that's what I was thinking.17:11
smcginnisI'll put it on my list and see if I can get to doing it any time soon.17:12
*** ricolin has joined #openstack-release17:12
*** hberaud has quit IRC17:24
*** hberaud has joined #openstack-release17:25
*** diablo_rojo has joined #openstack-release17:30
*** ekcs has joined #openstack-release17:36
*** ykarel|away has quit IRC17:51
*** electrofelix has quit IRC17:53
*** pcaruana has joined #openstack-release17:54
*** ricolin has quit IRC18:09
*** hberaud is now known as hberaud|gone18:11
*** diablo_rojo has quit IRC18:50
*** diablo_rojo has joined #openstack-release18:51
*** diablo_rojo_ has joined #openstack-release18:51
*** diablo_rojo_ has quit IRC18:51
openstackgerritLuigi Toscano proposed openstack/releases master: Second release of sahara-tests for Stein (0.9.0)  https://review.opendev.org/66802218:53
tonyb#startmeeting releaseteam19:00
openstackMeeting started Thu Jun 27 19:00:00 2019 UTC and is due to finish in 60 minutes.  The chair is tonyb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: releaseteam)"19:00
openstackThe meeting name has been set to 'releaseteam'19:00
ttxhi!19:00
tonybdiablo_rojo, smcginnis, dhellmann, armstrong, evrardjp: Release team meeting ping19:00
diablo_rojoo/19:00
smcginniso/19:01
tonybI suspect this is all we'll get today/tonight19:02
tonybOnly one topic for the agenda19:02
diablo_rojoGot all the cool kids though.19:02
diablo_rojo...I added a second topic but its not really important19:02
* fungi is not cool, but here anyway19:02
tonybdiablo_rojo: I see that19:03
tonybfungi: you are cool .... and you'll see I relied on your own notifications ;P19:03
tonyb#topic Review content for next proposed emails19:03
*** openstack changes topic to "Review content for next proposed emails (Meeting topic: releaseteam)"19:03
fungiindeed19:03
ttxYeah, so I've been reviewing the content for the next two, and I think we can just send one three weeks before M-2, one one-week before M-2 and one on M2 week19:03
tonyb#link https://etherpad.openstack.org/p/relmgmt-weekly-emails19:03
ttxOne key thing being you send on R-15 the one talkign about R-1419:04
ttxSo if you scroll down to R-15...19:04
ttxThat would be the one to send next week, to prepare R-1419:04
ttxOverall idea being to only send when we have somethign to say, rather than every week19:05
tonybttx: Just reading it/them19:05
ttxSounds like less work that way, and also less faigue in readers19:05
ttxfatigue19:05
smcginnisThat sounds like a good idea.19:05
ttxI only check-drafted the R-15 and R-13 ones19:05
smcginnisI did get a few folks saying they appreciated the countdown emails, but I think less often will be more useful as a good way to highlight things.19:06
ttxIf you look at the rest of the document, I propose similar skips19:06
ttxObviously starting at R-7 it's weekly19:06
diablo_rojo+219:06
ttxbecause we have different things to say every week19:06
tonybLooks good to me19:07
ttxtonyb: idea being to sdend teh email toward the end of the week, to prep for what needs to be done the coming week19:07
ttxOK, so if you all agree, I can translate that into tasks on the tracking etherpad19:08
tonybThanks ttx for bringing this up, diablo_rojo for pulling the data together and smcginnis for writing all the email last cycle we've used ;P19:08
tonybttx: I want to get in the habbit of sending them right after we close this meeting19:09
* diablo_rojo is a copy pasta pro19:09
ttx++19:09
tonybwhich will be much more doable with all this work in place19:09
smcginnisSome of that content is a few years old at this point. ;)19:09
ttxyeah, I did a gheavy rewite on the two I check-drafted so far...19:10
tonybWell thanks all round, I was struggling there a little19:11
diablo_rojoHappy to help :)19:12
ttxHmm we might need an email on R-8 about the extra-atcs-deadline in R-719:12
tonybttx: We can add it in the important dates now and then do the R-8 thing also19:13
smcginnisExtra ATC is really only useful now for allowing someone to vote, right?19:14
ttxOK, I moved things around19:14
ttxsmcginnis: yeah, arguably not a release thing19:14
ttxand more of a election official thing19:14
smcginnisStill useful to remind folks. I'm just thinking overall it's less important since not as many projects even need elections now and there is no free pass associated with that status.19:15
smcginnisJust thinking out loud really. Carry on. :)19:15
diablo_rojoI dont think it hurts to mention it.19:15
ttxwe can mention it on the '4 weeks before milestone-3" one19:15
ttxI dropped a note to remember19:16
tonybsmcginnis: but extra-atcs also get to vote for TC memebers19:16
tonybthanks ttx19:17
ttxSo the way it stands we'd send one on R-15 R-13 R-12 R-9 R-7 and then up to R-119:17
diablo_rojoLess than a dozen emails isnt so bad19:17
ttxAlso week after previous release, week before milestone-1 and week of milestone-1, but I haven't rewritten those19:17
fungiyes, election-related deadlines were included on the release schedule mainly out of convenience19:18
fungias they were generally tied to release cycles19:18
ttxSo please proofread the ones proposed for R-15 and R-13 when you get a chance19:18
diablo_rojoCan do19:18
tonybttx: \o/19:18
ttxI'll try to drop a base draft for them a couple of weeks before we need to send them, so as to not do them all at the same time19:19
tonyb#topic StoryBoard Backlog + Board19:19
*** openstack changes topic to "StoryBoard Backlog + Board (Meeting topic: releaseteam)"19:19
tonybdiablo_rojo says: I think the board is pretty out of date and we should probably prioritize some items for when people have free time (free time lol)19:20
tonyb#link https://storyboard.openstack.org/#!/board/6419:20
tonyb#link https://storyboard.openstack.org/#!/project_group/7319:20
tonybThere are probably also items that are done that can be marked as closed19:21
diablo_rojoHeh yeah. Was browsing SB the other day and I know we made some stories at the PTG, but that also some of them are done and I dont think its up to date.19:21
diablo_rojoThe board itself I think is behind a bit too? Not sure if there are other things we have in our backlog that should get prioritized19:21
fungithere's at least one assigned to me since ages i still haven't gotten around to doing19:21
fungi(sorry!)19:21
* diablo_rojo imagines everyone with the board and backlog open browsing19:22
smcginnisShouldn't things that are done automatically drop from the board?19:22
diablo_rojoNope. Its not using automatic worklists19:23
diablo_rojoIts a manual board/manual worklists19:23
smcginnisThen it's always going to be out of date. :/19:23
fungiyou can go tag the relevant stories and build automatic lanes based on tag+status queries19:24
diablo_rojoI think once people get their stuff merged, they should go ahead and move it to done or remove it frm the worklist19:24
fungii mean as an alternative to continuing with manual lanes19:25
fungione is more work up front, the other more work down the road19:25
fungialways a tradeoff19:26
tonybThe project group page is probably "okay" we just need to update status on som eof the items but board seems like it needs a lot ove work19:26
tonyb*of19:28
diablo_rojoI am happy to do a first pass of the board after we get the actual stories closed out that are completed.19:28
diablo_rojoI just dont know what all has been done.19:28
diablo_rojoThere were things marked as Stein..19:29
*** hberaud|gone has quit IRC19:29
tonybYeah I think most of the stuff on  https://storyboard.openstack.org/#!/board/64 is done19:29
diablo_rojoThats kinda what I had thought..19:30
tonybdiablo_rojo: I'll go through the board this week19:30
tonybthen we can review it in this meeting next week19:31
diablo_rojotonyb, let me know when you are and I can help.19:31
tonybI like the idea of "building all the automation" but I probably shoudln't ;P19:32
tonybdiablo_rojo: will do :)19:32
tonybdiablo_rojo: any afternoon that really works or sucks for you next week?19:32
diablo_rojoMonday would be good.19:33
diablo_rojoThe rest of the week I will be out because MURICA19:33
diablo_rojoand asettle and andymccr will be around19:33
diablo_rojoMy monday19:34
diablo_rojoyour Tuesday19:34
tonybdiablo_rojo: Okay, I'll see what I can do with my meetings19:34
tonyb#topic Open discussion19:35
*** openstack changes topic to "Open discussion (Meeting topic: releaseteam)"19:35
diablo_rojotonyb, cool. I can stick around later that day if you can't finagle meeting stuff19:35
smcginnisAs diablo_rojo alluded to, next Thursday is a holiday in the US. Most folks here have the day off from work.19:36
fungi(and are even likely to be nowhere near a computer!)19:36
smcginnisThere are enough non-US members here that I think a meeting could still be useful, but should probably expect a few of us to be AFK.19:36
tonybOh yeah .. and the meeting in Thursday19:36
fungifriday in tonyb's case ;)19:37
tonybsmcginnis: but if it's just ttx and I we could you know not do it at 2100/050019:37
smcginnisVery true! ;)19:37
fungiseems like a good opportunity to sleep in19:38
ttxhmm, would be good to at least do a go-nogo on the email?19:38
diablo_rojo+2 for sleeping in wherever possib;e19:38
diablo_rojopossible19:38
ttxbut that can be done through some async channel19:38
*** armstrong has joined #openstack-release19:39
tonybttx: Yeah, I have to leave early on Thursday so I don;t think we can do it earlyish your morning ...19:39
tonyblets do it async during the week19:40
ttxI mean, we could review it now too19:40
ttxI don;t expect anything new being discovered next week19:40
smcginnisGuessing it will be a quiet week.19:41
diablo_rojoYeah probably19:41
fungiif the gate catches fire and there's nobody around to notice, does it make a funny smell?19:42
tonybhehe19:42
tonybttx: mail on L253 LGTM ... much better than anything I could have written19:45
ttxtonyb: alright then, no need for meeting next week19:47
tonyb\o/19:47
tonybanything else?19:49
smcginnisHoliday for everyone. And Tony gets to sleep in. :)19:49
diablo_rojoNothing from me19:50
diablo_rojotonyb, just let me know when you wanna have the storyboard party19:50
diablo_rojoOther are of course invited too :)19:50
tonybdiablo_rojo: will do ;P19:50
tonybI s'pose I should make sure everyone knows that the week of the 8th I'll be totally AFK19:51
tonybno laptop19:51
tonybI will have my phone but I'll trry not to look at IRC/email19:51
smcginnisGood call.19:51
diablo_rojoSays the man with IRC on his phone lol19:51
tonybIt's true19:51
tonybFell free to ping me there but don't expect fast replies ;P19:52
tonyb*feel* even19:52
smcginnisNo free falling.19:52
diablo_rojosmcginnis, but skydiving is fun19:53
* ttx runs19:53
tonyb#endmeeting19:53
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at http://eavesdrop.openstack.org/irclogs/%23openstack-release/"19:53
openstackMeeting ended Thu Jun 27 19:53:48 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-06-27-19.00.html19:53
ttxCheers all, see you soon19:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-06-27-19.00.txt19:53
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-06-27-19.00.log.html19:53
tonybThanks everyone19:53
*** whoami-rajat has quit IRC19:54
fungithanks tonyb!19:54
diablo_rojoThanks tonyb!19:54
* diablo_rojo ducks out to grab lunch19:55
*** jtomasek has quit IRC19:55
*** diablo_rojo has quit IRC19:59
openstackgerritRyan Tidwell proposed openstack/releases master: Release neutron-lib 1.28.0  https://review.opendev.org/66804420:43
*** jtomasek has joined #openstack-release20:51
*** pcaruana has quit IRC21:05
*** diablo_rojo has joined #openstack-release21:10
*** jtomasek has quit IRC21:30
*** mriedem is now known as mriedem_afk21:45
*** armstrong has quit IRC22:19
*** mlavalle has quit IRC22:40
*** mlavalle has joined #openstack-release22:41
*** mlavalle has quit IRC22:41
*** tosky has quit IRC23:00
*** tonyb has quit IRC23:32
*** tonyb has joined #openstack-release23:32

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!