Thursday, 2019-03-07

*** tosky has quit IRC00:06
*** dave-mccowan has joined #openstack-release00:36
openstackgerritmelanie witt proposed openstack/releases master: osc-placement: release stein 1.5.0
melwittmriedem ^01:04
*** whoami-rajat has joined #openstack-release01:07
*** lbragstad has quit IRC01:09
*** dave-mccowan has quit IRC01:18
*** mriedem is now known as mriedem_afk01:51
*** mriedem_afk has quit IRC01:59
*** dave-mccowan has joined #openstack-release02:18
*** ekcs has quit IRC03:00
*** lbragstad has joined #openstack-release03:11
*** dtruong has quit IRC03:21
*** udesale has joined #openstack-release03:24
*** ricolin has joined #openstack-release03:48
*** ykarel_ is now known as ykarel04:00
*** dave-mccowan has quit IRC04:00
*** dtruong has joined #openstack-release04:03
*** ykarel has quit IRC04:07
*** ykarel has joined #openstack-release04:26
*** strigazi has quit IRC04:26
*** bnemec has quit IRC04:26
*** stephenfin has quit IRC04:26
*** huats has quit IRC04:26
*** dtruong has quit IRC04:45
*** strigazi has joined #openstack-release04:53
*** bnemec has joined #openstack-release04:53
*** stephenfin has joined #openstack-release04:53
*** huats has joined #openstack-release04:53
*** mjblack has quit IRC04:56
*** mjblack has joined #openstack-release04:58
*** ekcs has joined #openstack-release05:05
*** ricolin_ has joined #openstack-release05:07
*** ricolin has quit IRC05:09
*** lbragstad has quit IRC05:33
*** jhesketh has quit IRC05:53
*** jhesketh has joined #openstack-release05:54
*** ricolin_ has quit IRC06:09
*** ricolin has joined #openstack-release06:09
*** zbr has joined #openstack-release06:14
*** zbr|ssbarnea has quit IRC06:15
*** e0ne has joined #openstack-release06:32
*** jtomasek has joined #openstack-release06:45
*** jtomasek has quit IRC06:48
*** jtomasek has joined #openstack-release06:49
*** lxkong has quit IRC06:52
*** witek has joined #openstack-release07:04
*** ykarel has quit IRC07:04
*** ykarel has joined #openstack-release07:05
*** armax has quit IRC07:12
*** witek has quit IRC07:15
*** e0ne has quit IRC07:17
*** lxkong has joined #openstack-release07:21
*** e0ne has joined #openstack-release07:21
*** ekcs has quit IRC07:22
*** pcaruana has joined #openstack-release07:25
*** aojea has joined #openstack-release07:33
*** dtantsur|afk is now known as dtantsur07:55
*** tesseract has joined #openstack-release08:01
*** cgoncalves has joined #openstack-release08:03
*** e0ne has quit IRC08:04
cgoncalveshey release folks! any core available to review
*** tosky has joined #openstack-release08:27
evrardjpI didn't got the chance to review yesterday, so I am fixing that today.08:29
evrardjpcgoncalves: will do08:30
evrardjpcgoncalves: isn't this adding a new feature behind the scenes:
evrardjpI guess it's sync up though, so we could probably consider this as a bug08:34
*** jpich has joined #openstack-release08:44
cgoncalvesevrardjp, yeah, syncing up stuff. thank you!09:20
*** witek has joined #openstack-release09:28
*** ianw is now known as ianw_pto09:52
openstackgerritMerged openstack/releases master: Release python-monascaclient 1.14.0
openstackgerritMerged openstack/releases master: osc-placement: release stein 1.5.0
openstackgerritMerged openstack/releases master: Release python-octaviaclient 1.8.0 (Stein)
openstackgerritMerged openstack/releases master: python-tackerclient stein release 0.15.0
*** zbr|ssbarnea has joined #openstack-release10:17
*** zbr has quit IRC10:18
*** e0ne has joined #openstack-release10:25
openstackgerritMerged openstack/releases master: Cut stable/stein branch for kuryr
openstackgerritMerged openstack/releases master: Release kuryr-libnetwork 3.0.0
openstackgerritMerged openstack/releases master: Release python-zunclient 3.3.0
jaosoriorttx: regarding I did try to merge the fix for the README ... but it couldn't merge cause no jobs were running there... enabling the jobs leads to some failures that I am not able to reproduce locally, and haven't been able to fix.10:29
ttxjaosorior: ah. kind of a catch-22 there. Maybe that's one case where infra would be willing to force-merge the fix to unblock the knot. I'll bring it up at our team meeting this afternoon.10:33
jaosoriorttx: thanks, appreciate that10:33
*** cdent has joined #openstack-release10:33
*** ykarel is now known as ykarel|afk10:36
*** luizbag has joined #openstack-release10:36
*** ykarel|afk is now known as ykarel10:43
*** odyssey4me has quit IRC10:53
*** odyssey4me has joined #openstack-release10:53
*** jpich has quit IRC10:55
*** ykarel is now known as ykarel|afk10:56
*** jpich has joined #openstack-release10:57
openstackgerritRenat Akhmerov proposed openstack/releases master: Release Mistral Stein 3
*** zbr has joined #openstack-release10:57
*** udesale has quit IRC10:59
*** udesale has joined #openstack-release10:59
*** zbr|ssbarnea has quit IRC10:59
*** ifat_afek has joined #openstack-release11:09
*** ykarel|afk is now known as ykarel11:15
*** zbr|ssbarnea has joined #openstack-release11:17
*** dtantsur is now known as dtantsur|bbl11:19
*** zbr has quit IRC11:19
*** ricolin has quit IRC11:20
*** udesale has quit IRC11:28
*** electrofelix has joined #openstack-release11:42
*** udesale has joined #openstack-release11:45
*** zbr has joined #openstack-release11:46
*** zbr has quit IRC11:46
*** zbr has joined #openstack-release11:47
*** zbr|ssbarnea has quit IRC11:48
openstackgerritTom Barron proposed openstack/releases master: Release manila client 1.27.0
openstackgerritJuan Antonio Osorio Robles proposed openstack/releases master: TripleO: minor release for rocky
*** dave-mccowan has joined #openstack-release12:22
*** ricolin has joined #openstack-release12:27
*** udesale has quit IRC13:02
*** udesale has joined #openstack-release13:08
openstackgerritJuan Antonio Osorio Robles proposed openstack/releases master: TripleO: minor release for rocky
*** ykarel_ has joined #openstack-release13:14
*** ifat_afek has quit IRC13:16
*** ykarel has quit IRC13:17
*** ykarel_ is now known as ykarel13:21
cdentsmcginnis: if there such a thing a client lib final release exception? see the discussion near the end of
*** mriedem has joined #openstack-release13:30
e0nehi team. if we didn't do stein-2 release for horizon, what version should I specify for stein-3?13:40
e0newe've got version: for stein-113:40
openstackgerritIvan Kolodyazhny proposed openstack/releases master: Release Horizon stein-3
*** lbragstad has joined #openstack-release13:48
*** dtantsur|bbl is now known as dtantsur14:10
smcginnise0ne: You got it right. This is the second beta release, so .0b2 is correct.14:21
smcginniscdent: There is the requirements feature freeze exception.14:22
e0nesmcginnis: ok, thanks for the confirmation14:22
smcginniscdent: We may want to do a release with what is merged now. Then ask for a FFE for this once it merges.14:22
smcginnisSo at least everything else is made available right away.14:22
cdentsmcginnis: there was supposed to have been an osc-placement release last night14:22
smcginniscdent: I think I saw that.14:23
cdenti'm not aware of it showing up a requirement for service projects14:23
cdentso it's mostly a matter of "do we want to get these features out to deployers for stein"14:23
cdentwhich, yes, it would be nice14:23
smcginnisIf no one is consuming it, that makes it easy. Low risk.14:23
cgoncalvessmcginnis, hi. any chance you could +W ? it prevents us in octavia from verifying and merge a feature14:27
smcginniscgoncalves: Sure, I will take a look shortly.14:28
openstackgerritEric Fried proposed openstack/releases master: Release python-novaclient 12.1.0
*** mriedem is now known as mriedem_afk14:34
cgoncalvessmcginnis, thank you!14:37
smcginniscgoncalves: No problem! I'll try to watch for the requirements update too and help that through.14:38
*** mriedem_afk is now known as mriedem14:46
openstackgerritMerged openstack/releases master: Release octavia-lib 1.1.1
openstackgerritAkihiro Motoki proposed openstack/releases master: neutron Stein-3 beta deliverables
openstackgerritAkihiro Motoki proposed openstack/releases master: python-neutronclient 6.12.0 (Stein)
toskyI always forget when the branching happens - is it going to happen tomorrow, next week, or during the RC week?14:51
openstackgerritJeremy Freudberg proposed openstack/releases master: Release python-saharaclient 2.2.0
fungitosky: at rc114:58
smcginnistosky: Clients can already branch is you don't think there is much risk of needing to backport bugfixes yet for stein.14:58
smcginnisService projects should be at the RC1 though.14:59
fungieubsequent rc tags and release tag wind up on the stable/stein branch14:59
fungier, subsequent14:59
toskyfungi, smcginnis : thanks! I think I went through but I was not totally sure14:59
smcginnisI do mention it in the last couple countdown emails -
toskyuh, right15:01
smcginnisSOrry, not saying RTFM, just confirming with myself that I didn't forget about it. ;)15:01
toskyalso: do I remember correctly that the devstack and grenade branching is a usually bit delayed?15:04
smcginnistosky: Yeah, looks like that happens post-RC1 once most projects are ready for it.15:08
smcginnisAgain, not saying to read the manual, just making sure we have it documented. ^ :)15:08
toskysure, I asked because I remember that sometimes it happens not exactly during the RC week, even if the text may imply that15:10
toskysometimes the delay has been... remarkable :)15:10
toskythanks again15:11
smcginnisI think it's a combination of projects actually being ready, and QA team doing the final steps needed on the devstack and grenade side.15:11
smcginnisHopefully that's better now.15:11
toskyso I need to hurry up with my native Zuul v3 grenade job; it's almost working now15:11
* smcginnis crosses fingers15:11
toskyI mean, it seems to be working even with some plugins, I need to fix the logging15:12
smcginnisGreat! I think other projects could benefit from seeing that work done elsewhere.15:12
cgoncalvessmcginnis, :)15:14
*** tellesnobrega has joined #openstack-release15:21
tellesnobregahi folks, I'm cutting versions for the sahara plugins (new in stein) and I'm wondering if we should have the plugin version set to the same on sahara (10.*)15:22
tellesnobregaor should we start from 1?15:22
smcginnistellesnobrega: It's best to start from 1.15:25
tellesnobregathanks smcginnis15:25
*** ykarel is now known as ykarel|away15:29
openstackgerritEric Fried proposed openstack/releases master: Release python-novaclient 13.0.0
smcginnis#startmeeting releaseteam16:00
openstackMeeting started Thu Mar  7 16:00:01 2019 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: releaseteam)"16:00
openstackThe meeting name has been set to 'releaseteam'16:00
smcginnisevrardjp: Quick!16:00
smcginnisPing list: smcginnis ttx dhellmann diablo_rojo hberaud evrardjp fungi armstrong16:00
smcginnis#link Agenda16:00
smcginnisWaay down around line 387 now.16:00
*** mlavalle has joined #openstack-release16:00
smcginnisThank you as usual to ttx for getting an agenda together there.16:00
*** armstrong has joined #openstack-release16:00
smcginnisAt least I assume it was ttx. :)16:01
smcginnisMorning fungi16:01
*** udesale has quit IRC16:01
ttxyes I'm to blame16:02
evrardjpfungi: always sending me a holiday vibe16:02
smcginnis#topic Queens Tripleo release16:02
*** openstack changes topic to "Queens Tripleo release (Meeting topic: releaseteam)"16:02
smcginnisREADME issued blocked on being able to merge to stable.16:03
smcginnisI wasn't aware of these. I suppose they could switch over to noop, get this merged, then switch mack and figure things out.16:04
ttxyeah they are blocked so I wanted to discuss a solution there16:04
smcginnisttx: Did you have something in mind?16:04
ttxLooks like for some reason the jobs were disabled on Queens16:05
ttxand now that they are trying to reenable them to get this technical change merged they see they are broken16:05
ttxso I was windering if we should just not force-merge them, since it's extremely likely to be a one-off16:05
ttxmaybe fungi has an opinion on that :)16:06
fungiyeah, i'm trying to digest the problem16:06
* evrardjp takes popcorn16:06
smcginnisSeems like they should get things fixed, but that would work to get things going for now.16:06
ttxI guess they could just set noop instead of the set of failing jobs16:07
fungithey want to tag a new point release of tie from stable/queens?16:07
evrardjpor just remove openstack-python-jobs16:07
ttxI think they want to do a new tripleo release, and that includes some repo that they are no longer updating16:07
fungiand their python 2.7 unit tests no longer work on that branch?16:07
ttxexcept that our validation is now catching README formatting, so they kind of need to fix that16:08
ttxso they are trying to, but they get no job to match, and adding the ones previously defined kinda fails16:08
ttxHaven't gone deeper in the rabbit hole as to WHY those long-dead jobs tdo not work when reanimated16:09
fungiyeah, i don't know how to set the no-op job just for specific branches of a repository but i can ask a few others16:09
evrardjpsorry to be selfish here16:09
ttx I feel like we should just force-merge it as it's really the only thing that will land there16:09
smcginnisSomething seems off about wanting to release something that can't pass unit tests. Really feels like they should fix things first.16:09
ttxrather than spend time "fixing" it16:10
evrardjpbut shouldn't the team fix it in a one off to do this?16:10
smcginnisAnd really seems like an issue for that team to figure out. Not really a release issue.16:10
evrardjpthat's what I meant -- they are in charge of their destiny?16:10
fungiskimming the job log, it looks like some specific unit tests in there are failing16:10
ttxThat said, yes it's a bit weird tat they would want to do a release for something they can no longer fully test16:10
evrardjpyup -- TestOsSvcDaemon.test_dir_only_upstart or something16:11
fungiso maybe an easy suggestion is that they skip those specific unit tests in their py27 job16:11
smcginnisThey could also drop that repo from the release request and get everything else out.16:11
evrardjpI think they should just fix it16:11
fungiif they're not maintaining it, why does it need a new point release anyway?16:11
ttxbut then the deliverable will appear incomplete16:11
evrardjpif you release it, it sends a message, right?16:11
ttxfungi: yeah that is the point I raised just above16:11
fungibut also, if they're not maintainind some particular repository in a deliverable and maintaining others, then it's not the same deliverable is it?16:12
ttxhappy with any outcome really -- we just need to tell them the best way out16:12
smcginnisDo "we"?16:12
fungiwe can certainly present them with some of the options we came up with, but as to which is "best" that's likely up to them to decide16:12
evrardjpfungi: ++16:13
evrardjpwe could also recommend what we consider best16:13
evrardjpfrom our perspective16:13
fungijaosorior, as ptl, can also just read the above for our list of suggestions16:13
ttxok, if no easy solution let's not spend the whole meeting on this16:13
evrardjpbut then they take the decision :)16:13
evrardjpttx: agreed16:13
smcginnisI agree. We can give suggestions as a group of people who care, but I don't think this is anything on the release team to sort out.16:13
ttxand schedule a discussion with jaosorior to walk through it16:13
smcginnisAny more on this topic?16:14
smcginnis#topic Review R-5 week tasks16:14
*** openstack changes topic to "Review R-5 week tasks (Meeting topic: releaseteam)"16:14
ttxI see two open tasks16:15
ttxGenerate release requests... (diablo_rojo and evrardjp)16:15
smcginnisThe first I can include in the countdown email.16:15
ttxFreeze changes... (prometheanfire)16:15
smcginnisOh, looking at next week's tasks.16:15
ttxsmcginnis: that's next topic :)16:16
smcginnisI believe diablo_rojo is ready to go on those release requests.16:16
diablo_rojosmcginnis, correct16:16
diablo_rojojust regenerated the list and put it in the etherpad16:16
evrardjpI think ttx has an opinion on this16:16
smcginnisThanks diablo_rojo and evrardjp for going through getting ready for that last week.16:16
diablo_rojoits the same as it was16:16
diablo_rojoI had already accidentally pushed the pankoclient patch16:17
ttxI did record my opinion at
* dhellmann slips into the back of the room late16:17
evrardjpttx: beat me to it :)16:17
ttxi.e. we should release libraries that have not been released since milestone-216:17
ttxthat is what we said we'd do16:18
ttxand announced in email at the start of the cycle16:18
smcginnisRight, we stated we would release c-w-i libs at each milestone.16:18
smcginnisAs long as there was something to release.16:18
ttxRegarding tooling ISTR we had a magic CLI for that... dhellmann ?16:18
evrardjpthen yes somethign might have slipped through the cracks then16:18
smcginnisBut we also need to release the ones that didn't have anything to release previously so we have a branching point.16:19
ttxsmcginnis: and as long as they were not released otherwise in that same timeframe16:19
dhellmannwe have propose-library-branches16:20
dhellmannand propose-final-releases but I don't know if that works for just libraries; I think that's about RC->final transition16:20
ttxbut not list-deliverables --unreleased-since <date>16:20
smcginnisNo scripts that will generate the release requests, but can at least tell us what has not been released.16:21
evrardjpsmcginnis: I didn't think we had something based on date.16:21
dhellmannah, no, not based on date16:21
ttxfwiw that same script is supposed to help at milestone-1 and milestone-2 too :)16:21
evrardjpsmcginnis: problem is that we can't presume the release anymore16:21
dhellmannthat would be a good tool to have, though16:21
evrardjpbecause ppl are not forced to create for milestone x anymore16:22
evrardjpif I understood correctly16:22
dhellmannI think I expected us to just use list_library_unreleased_changes.sh16:22
ttxdhellmann: i mean, we'd really be grateful if that script existed, right16:22
dhellmannanything that has changes needs to be released, including if they are just for tests16:22
dhellmannttx: I will buy the author a beer16:22
smcginnisdhellmann: ++16:22
evrardjpttx: wow that wink crossed the oceans.16:22
ttxdhellmann: I will buy the author a glass of wine.16:23
evrardjpoh wait I have the impression this will backfire16:23
dhellmannthat escalated quickly16:23
smcginnisSo we have two things. Ones that haven't done any release yet that we can get with --unreleased, but that would also be included (presumable) in
evrardjpdhellmann: want me to help there -- I think I would like to spend time on tooling, to refresh my knowledge, and clean what's not required if we can16:24
evrardjpsorry wrongly phrased16:24
dhellmannsmcginnis : maybe not, if they haven't landed any changes16:24
evrardjpdhellmann: do you want me to help there?16:24
ttxIt's also fine to generate them manually for this tmie, to see what's expected16:24
smcginnisevrardjp: That would be great. It could use some attention I'm sure.16:24
smcginnisdhellmann: True, there might be a few outside of that venn diagram overlap.16:24
evrardjpttx: probably best, because I am not sure when I will have time on this16:24
dhellmannevrardjp : I'm not going to have time to do it, but I would be able to advise a bit16:25
openstackgerritEric Fried proposed openstack/releases master: Release python-novaclient 13.0.0
dhellmannevrardjp : so if you want to own it that would be great16:25
dhellmanngenerating the actual releases could be scripted by calling new-release repeatedly once there is a list of the things that needs the releases16:25
smcginnisYou could do it manually for now and make sure the necessary steps are written down. Then at some point use that documentation to automate.16:25
dhellmannif you start with the ones that are completely unreleased then it will make looking at the output of less of a chore16:25
evrardjpdhellmann: I think that's what in my pseudo code in my patch16:26
diablo_rojoI will get the patches for unreleased libs up today for you evrardjp16:26
evrardjpbut does list_library_unreleased_changes know about milestones?16:26
ttxok, let's move on --- I wrote down that evrardjp and diablo_rojo would work to generate those manually16:27
coreycbhi all, does anyone know how i'd go about getting a 2.3.1 release of ldappool for stable/rocky? since it's an independent deliverable it's not obvious to me what is needed.
evrardjplgtm ttx16:27
evrardjpdiablo_rojo: we'll do this together :)16:27
ttxthe other item -- I haven't heard of prometheanfire this week16:27
evrardjpI am just thinking of the next cycle at the same time :p16:27
smcginnisevrardjp: No, but if you get ones that haven't released at all, then any others that have changes that have not been released can be released.16:27
diablo_rojoevrardjp, sounds good to me16:27
smcginniscoreycb: It would not be for rocky since it's independent.16:28
ttxbut since the deadline is not there yet, I don't think we need to organize search and rescue just yet16:28
evrardjpsmcginnis: I didn't know we had the tooling for the ones with changes unreleased. That script name makes more sense to me know16:28
smcginnisOK, let's move on and we can work through any more details out of meeting.16:28
smcginnis#topic Library freeze exceptions16:28
*** openstack changes topic to "Library freeze exceptions (Meeting topic: releaseteam)"16:28
coreycbsmcginnis: ok. is it possible for me to update upper-constraints for stable/rocky ldappool?16:29
smcginnisWe did release octavia-lib today.16:29
ttxyeah I spotted a lib release that was post-freeze... but it's bugfix enough I think16:29
smcginnisThey had issues that required a new release.16:29
ttxhappy to approve if everyone is happy with it16:29
ttxoh it's done16:30
ttxnext topic :)16:30
smcginnisI figured we would get that in the requirements update review if prometheanfire wanted an official FFE on that.16:30
ttxAny missing library release ?16:30
* coreycb apologizes for interrupting a meeting16:30
smcginniscoreycb: No worries, sorry.16:30
ttxor did we cover them all last week ?16:30
smcginnisI believe we got all the libs, but we should double check that.16:31
ttxos-client-config is the only one that shows as completely unreleased16:32
smcginnisI think I had asked Monty about that one, but not sure if we got an answer.16:33
ttxthe others might not be recent (i.e. released since milestone-2)16:33
ttxpycadf, shade had a single release16:34
fungimordred is around, i think16:34
smcginnisHmm, I see os-brick changes that should have gone out.16:34
mordredwhat did I do?16:34
mordredoh. poo. one sec16:34
dhellmannos-client-config has a fair number of changes, including test job stuff16:34
ttxsame for automaton blazar-nova ceilometermiddleware cliff debtcollector kuryr mistral-lib mox3 os-acc16:35
mordredyeah. sorry - we should likely cut a shade release16:35
ttxthose had a single release in stein ^16:35
ttxwhich might or might not be recent16:35
* ttx manually checks16:35
ttxpycadf - 5 weeks ago16:36
openstackgerritMonty Taylor proposed openstack/releases master: Release 1.31.0 of shade
ttxautomaton = 6 days ago16:36
ttxblazar-nova = 6 days ago16:37
fungimordred: the bigger question was around os-client-config16:37
ttxsame for ceilometermiddleware16:37
ttxcliff - 4 months ago16:37
mordredyeah - it's mostly test fixes - there's one patch that might be release worthy16:37
dhellmannmordred : at this point, we want a release so when we branch those test fixes end up in your stable branch16:38
ttxdebtcollector - 7 days16:38
mordreddhellmann: ++16:38
ttxkuryr - 7 weeks16:38
dhellmannso anything with any unreleased patches of any type should be released16:38
ttxmistral-lib - 6 days16:38
ttxmox3 - 7 days16:39
dhellmanns/anything/any library/16:39
ttxos-acc - 4 months16:39
openstackgerritMonty Taylor proposed openstack/releases master: Release 1.32.0 of os-client-config
dhellmannit sounds like we have a lot of tags to generate16:39
ttxI only checked those who released only once in the cycle as good candidates16:39
mordredthere ya go - sorry about that16:40
ttxI'd say kuryr, cliff, and os-acc might need a refresh16:40
ttxthe others should be "fresh enough"16:40
smcginnisWe must need better documentation on generating those lib releases. The ones 6 days ago must have been picked up by the script. Not sure why the older ones were not though.16:41
dhellmannthe only change in kuryr is to add the python 3.7 job16:42
ttxok so the one release they have is good enough16:42
dhellmanncliff has a lower-constraints template change, we should probably tag that16:42
dhellmannos-acc has no changes16:42
ttxdhellmann: can you generate the cliff release req?16:43
evrardjpsmcginnis: I agree16:43
ttxsmcginnis: yes we need a tool16:43
ttxin the mean time this manual checking will do16:43
openstackgerritDoug Hellmann proposed openstack/releases master: cliff 2.14.1
ttxok all set16:45
openstackgerritKendall Nelson proposed openstack/releases master: Release python-aodhclient 1.2.0
smcginnis#topic Client library freeze16:45
*** openstack changes topic to "Client library freeze (Meeting topic: releaseteam)"16:45
smcginnisSo still a few with no releases.16:45
smcginnisWe have several hours to go yet though.16:46
ttxthose are supposed to be caught by the task we already talked about16:46
ttxMaybe y'all can use the etherpad as a tracking mechanism as you go through them manually16:46
ttxthat way we can play too16:47
smcginnisWell, maybe that's an opportunity for more documention. We need need to capture the non-client lib ones at that deadline, then wait until end of today for the client lib ones.16:47
dhellmannunreleased changes in client libraries:
smcginnisSo really we need to rerun this client list tomorrow morning and see what ultimately missed today's deadline.16:48
smcginnisevrardjp, diablo_rojo: Are you two on that task? Tomorrow get the final list and propose releases for any client libs that missed?16:49
diablo_rojosmcginnis, yep I got it16:50
smcginnis++ Thanks!16:50
evrardjpthanks diablo_rojo16:50
smcginnisOverall I think it doesn't look too bad so far.16:50
diablo_rojoOnly 616:50
smcginnisWe've seen worse. ;)16:50
smcginnis#topic Cycle highlights collection16:51
*** openstack changes topic to "Cycle highlights collection (Meeting topic: releaseteam)"16:51
diablo_rojoI have an email drafted ready to send16:51
smcginnisI had a blurb in the last countdown.16:51
diablo_rojoI can click the button whenever16:51
diablo_rojoI took from you original introduction to remnind folks of the importance and how to16:52
smcginnisIf you want to send that now, I can add a reference to that in the countdown email I send out to try to increase odds someone reads them.16:52
diablo_rojoCan do16:52
smcginnisGreat, I'll grab the link and add it.16:52
smcginnis#topic Forum brainstorming16:53
*** openstack changes topic to "Forum brainstorming (Meeting topic: releaseteam)"16:53
*** tellesnobrega has left #openstack-release16:53
ttxI was wondering if we wanted to submit anything16:53
ttxit closes tomorrow-ish (or was it extended ?)16:54
smcginnisBen was going to submit a PTL feedback session that we had talked about piggybacking on to get release process change feedback.16:54
smcginnisI didn't have anything else that I could think of needing.16:54
diablo_rojosmcginnis, extended till the 10th16:55
smcginnisOK, great.16:55
smcginnisAnyone have any Forum appropriate release topics in mind?16:55
fungiprocrastinators rejoice!16:55
dhellmanndo we have a schedule for train settled?16:55
diablo_rojoNot that I can think of?16:55
evrardjpsmcginnis: it's not listed in Ben session's draft though16:55
smcginnisWe will also have at least some hallway time during the PTG for release-specific topics.16:55
evrardjpso we probably want to make sure PTLs are there by doing proper publicity of it16:55
dhellmannI can imagine teams wanting to know by the ptg/forum16:55
smcginnisdhellmann: I have a proposed schedule up.16:56
smcginnisThat would be good to finalize that.16:56
dhellmannok, I wasn't sure if the dates were firm -- yeah16:56
smcginnisNot firm until we approve it, but no one has pointed out major issues with the dates yet.16:56
ttxmaybe we should now16:57
smcginnisIf it's good enough, maybe we should get that approved so it's published and we can get broader community feedback if there is anything that doesn't land at a  good time.16:57
ttxIt's FF after all16:57
dhellmannworks for me16:58
smcginnisFor your easy viewing pleasure.16:58
ttxI would just approve it and send "this is it, if we missed something critical just let us know asap" email16:58
diablo_rojoHehe.. yeah.. I think doing elections is going to suck this round.16:59
smcginnisI could mention in the countdown, but then also send its own ML post to increase odds of someone actually seeing it.16:59
diablo_rojoIf the goal is high visibility I think its own email would be better16:59
dhellmannyeah, separate email thread16:59
dhellmannand we should get the election officials to add those dates as early as we can17:00
prometheanfiresmcginnis: what's up?17:00
fungii'm open to brainstorming easier ways of handling the election scheduling for next round though i also can't be an official17:00
fungiunless i decide not to run for the tc again that is17:00
smcginnisUmm, think we had mentioned requirements freeze and that there are one or two libs that may or may not need to ask for an official FFE.17:00
diablo_rojodhellmann, thats going to require another tc convo I think. tonyb projected the dates and they look pretty simultanrous17:00
dhellmanndiablo_rojo : ok. that's one for mnaser then17:01
openstackgerritDuc Truong proposed openstack/releases master: Release python-senlinclient 1.11.0 (Stein)
diablo_rojofungi, yeah and if I ever want to run.. then it would be one less too17:01
smcginnisI think the only question on the schedule related to that was ATC deadline. That can be moved afterwards if it's determined it's not enough time.17:02
diablo_rojodhellmann, yeah I figured after this schedule got set we would bring it up in office hours or something17:02
ttxwe have one more topic, task assignment17:02
dhellmanndiablo_rojo , fungi : I might be talked into helping. I can't promise this early, though.17:02
smcginnisttx: Are you good with the propsoed train schedule?17:02
fungidhellmann: thanks, we'll keep that in mind17:02
diablo_rojodhellmann, noted :D17:02
smcginnisDoes someone want to approve that? Then I can get emails sent.17:03
fungi(it is mostly automated at least)17:03
smcginnis#topic Assign R-4 week tasks17:03
*** openstack changes topic to "Assign R-4 week tasks (Meeting topic: releaseteam)"17:03
*** dtruong has joined #openstack-release17:03
smcginnisThe first task for next week I can include in the countdown email.17:03
ttxThe warn task should probably just be a weekly email thing17:03
smcginnisThe next task is thankfully a nicely scripted one.17:04
ttxI'm happy to take the second one unless someone wants it17:04
smcginnisdiablo_rojo and evrardjp: Up for another one?17:04
smcginnisOr ttx17:04
ttx(I'll be around that week)17:04
evrardjpI am not around next week17:04
smcginnisOh right, I should point out I'm at the Open Source Leadership Summit next week, so my availability will be spotty.17:04
diablo_rojosmcginnis, such a leader ;)17:05
*** tesseract has quit IRC17:05
smcginnisOK, I'll put ttx down as owning the branching task.17:05
smcginnisOK, we're over. Anything else?17:05
ttxsmcginnis: I'm not an open source leader so I'm not invited :P17:05
evrardjpttx: FOMO?17:06
ttxall done thx!17:06
diablo_rojoevrardjp, always17:06
smcginnisOK, thanks everyone!17:06
ttxevrardjp: I *almost* submitted a talk but then decided to not travel THAT much17:06
diablo_rojothanks smcginnis17:06
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at"17:06
openstackMeeting ended Thu Mar  7 17:06:30 2019 UTC.  Information about MeetBot at . (v 0.1.4)17:06
openstackMinutes (text):
fungithanks smcginnis!17:06
fungi#link OpenStack Infra (Train Cycle) artifact signing key17:06
fungihas a few root sysadmin signatures published for it now if any release managers are interested in doing the same17:06
smcginnisNice thing about doing this in our own channel, we can really go as long as we want.17:07
smcginnisThanks fungi17:07
*** e0ne has quit IRC17:07
evrardjpsmcginnis: you closed it earlier though :p17:07
fungi(was saving that for open discussion, but we didn't have one)17:07
smcginnisfungi: How does one go about doing the same?17:07
evrardjpI suppose trusting the key signing it and push it servers?17:07
evrardjpnoob to this17:07
evrardjpor do you want something else?17:08
fungismcginnis: short answer is to fetch the key, check the signatures appear to be from keys of folks whose keys you've previously signed and trust, then sign that key and push your copy of it back to the keyserver network17:08
smcginnisfungi: Any instructions somewhere on how that's all done?17:08
fungithat's the long answer ;)17:09
fungilemme see what i can get you17:09
* smcginnis has never really worked with public keyservers17:09
openstackgerritKendall Nelson proposed openstack/releases master: Release python-aodhclient 1.2.0
fungifor the sysadmins we have but they're expected to actually inspect the key on our server's filesystem before attesting to it, so the steps for retrieving the key from the keyserver network and verifying the signatures on it are going to be somewhat different17:10
smcginnisCool, thanks.17:11
fungiif you're looking for a recommended configuration using the sks keyservers, we have
openstackgerritMerged openstack/releases master: Proposed release schedule for Train
fungithat example configuration relies on some fancy newer protocols which further secure your communication with the keyservers17:12
fungiwhere "newer" is taken to mean "from this century"17:13
*** ekcs has joined #openstack-release17:13
*** armax has joined #openstack-release17:16
fungismcginnis: to retrieve that key for inspection, you can `gpg2 --recv-keys 0xcdc08088c3cb45a9be08332b2354069e5b504663`17:17
fungiand then `gpg2 --check-signatures 0xcdc08088c3cb45a9be08332b2354069e5b504663` to see if the signatures are from keys you already know/trust17:19
funginote that --list-signatures will also show signatures from keys which are not known to your current keyring17:21
smcginnisCool, looks like I've at least gotten that far.17:22
*** ricolin has quit IRC17:22
smcginnisfungi: I have two signing keys. Do you happen to know offhand how to switch which one is used as default.17:23
smcginnisI should have the answer shortly, but figured I'd ask if you just knew it.17:23
fungismcginnis: in my ~/.gnupg/gpg.conf i use "default-key 0x48f9961143495829"17:24
smcginnisAh, perfect. Thanks fungi17:24
fungibecause my keyring also contains an older, weaker key i transitioned off of more than a decade ago17:24
*** dtantsur is now known as dtantsur|afk17:34
*** ykarel|away has quit IRC17:43
*** smrcascao has quit IRC17:57
*** mriedem is now known as mriedem_afk17:58
*** ekcs has quit IRC18:00
*** irclogbot_2 has joined #openstack-release18:03
*** zbr|ssbarnea has joined #openstack-release18:11
*** witek has quit IRC18:13
*** zbr has quit IRC18:13
*** e0ne has joined #openstack-release18:19
*** jpich has quit IRC18:20
*** e0ne has quit IRC18:24
*** e0ne has joined #openstack-release18:29
openstackgerritErno Kuvaja proposed openstack/releases master: Release python-glanceclient 2.16.0 for Stein
*** e0ne has quit IRC18:33
smcginnisfungi: Well, I must have gotten it mostly right -
*** mriedem_afk is now known as mriedem18:40
*** ekcs has joined #openstack-release18:41
*** pcaruana has quit IRC18:46
openstackgerritJulia Kreger proposed openstack/releases master: Release python-ironicclient 2.7.0 for stein
openstackgerritJulia Kreger proposed openstack/releases master: Release python-ironic-inspector-client 3.5.0 for Stein
*** pcaruana has joined #openstack-release19:05
openstackgerritMerged openstack/releases master: Release Mistral Stein 3
openstackgerritTelles Mota Vidal Nóbrega proposed openstack/releases master: Release of all Sahara Plugins
*** electrofelix has quit IRC19:14
openstackgerritMerged openstack/releases master: Release Vitrage deliverables
openstackgerritMerged openstack/releases master: Release manila client 1.27.0
openstackgerritMerged openstack/releases master: Release Horizon stein-3
*** luizbag has quit IRC19:28
*** pcaruana has quit IRC19:33
*** tellesnobrega has joined #openstack-release19:34
*** ekcs has quit IRC19:34
tellesnobregasmcginnis, can you help me understand what is the issue with
*** armstrong has quit IRC19:40
*** ekcs has joined #openstack-release19:43
dhellmanntellesnobrega : the release job is going to want to publish those deliverables to pypi and to do that it tries to verify that it can. That verification is failing because they either don't exist on pypi or the openstackci user does not have permission to publish.19:49
dhellmannfrom checking sahara-plugin-cdh my guess is that they do not exist at all19:49
tellesnobregaI don't think they exist on pypi yet19:53
dhellmanntellesnobrega : ok, so you should be able to follow the infra manual instructions to fix that:
openstackgerritAndrey Kurilin proposed openstack/releases master: [rally] Release rally-openstack 1.4.0 package
*** e0ne has joined #openstack-release20:35
*** ifat_afek has joined #openstack-release20:38
*** aojea has quit IRC20:39
*** ifat_afek has quit IRC20:55
*** armax has quit IRC21:03
*** e0ne has quit IRC21:14
*** whoami-rajat has quit IRC21:17
*** mtreinish has quit IRC21:25
*** mtreinish has joined #openstack-release21:26
*** smrcascao has joined #openstack-release21:36
*** waverider has joined #openstack-release21:56
*** e0ne has joined #openstack-release22:01
*** dave-mccowan has quit IRC22:02
*** tosky has quit IRC22:22
*** tosky has joined #openstack-release22:29
*** cdent has quit IRC22:33
*** e0ne has quit IRC22:34
*** e0ne has joined #openstack-release22:35
*** e0ne has quit IRC22:36
*** armax has joined #openstack-release22:44
*** waverider has quit IRC22:53
*** ekcs has quit IRC22:59
*** mriedem is now known as mriedem_away23:02
tellesnobregadhellmann, thanks23:04
*** ekcs has joined #openstack-release23:05
dhellmannsmcginnis : I wonder if it would be a good idea to automate setting up pypi to register a project if it's not found23:11
tellesnobregadhellmann, apparently it is already23:15
tellesnobregatosky pointed out to me that fungi told him that we didn't need to create the projects on pypi because it automagically works from release jobs23:16
smcginnisThat must have changed.23:16
smcginnisI wonder how that can be automated. I suppose if it's all done under the openstackci account it should be able to do all the steps.23:16
toskyfrom December?23:16
toskythis is the past discussion:
smcginnisfungi: Are you still around? Can you confirm? If so, we will need to remove that check from our validation.23:17
dhellmannso we should probably change our validation to pass if the project does not exist on pypi since it can be created properly, but we should continue to check for failure if the project exists and we do not have permission23:18
smcginnis++ Exactly what I was thinking.23:18
smcginnisI can grab that if you want/23:18
tellesnobregawhat should I do from the sahara point of view? just wait for the update and recheck?23:19
smcginnistellesnobrega: I guess so.23:20
dhellmannwe could throw up a patch to remove that check, rebase the sahara release on top of it, then add another one to restore it23:21
dhellmannthat would let us go ahead until we get the more complicated check written23:21
smcginnisdhellmann: Looks a little more complicated in that we don't actually check if it exists or not. Do you know if there is a simple pypi API for that to just do a quick check up front.23:21
dhellmannit looks like we could use get_pypi_info() to tell if the project exists23:23
dhellmannI guess the xmlrpc API just returns an empty list of roles if the project does not exist23:23
smcginnisHmm, is this right? "url = '{}/json'.format(canonical_name)"23:25
smcginnisGets a 404 from my test -
smcginnisShoot, I need to go. I'll check back later.23:26
*** ekcs has quit IRC23:28
tonyb[m]Oh that 301's to
tonyb[m]so use that I guess23:28
tonyb[m]"curl -s | jq ." works for me23:29
dhellmannyeah, I think someone came through and did a global search and replace of and we didn't fix the path23:30
tonyb[m]well requests etc will handle the 30123:30
smcginnisThe path in code is wrong.23:31
dhellmannis one of you working on the patches, or should I?23:33
dhellmannI have a few minutes before dinner...23:33
dhellmanntonyb[m] ?23:33
*** tosky has quit IRC23:34
openstackgerritDoug Hellmann proposed openstack/releases master: Release of all Sahara Plugins
openstackgerritDoug Hellmann proposed openstack/releases master: fix URL in get_pypi_info()
openstackgerritDoug Hellmann proposed openstack/releases master: only fail pypi permission validation if the project exists
dhellmannthat should do it ^23:35
tellesnobregadhellmann, thanks :)23:36
tonybdhellmann: Wow we can create projects?  I dind't knwo that I thought they needed to be pre-created and setup23:37
dhellmannthe only way to create them now is through twine and uploading a package23:37
dhellmannso if it doesn't exist, it is created automatically by the release23:37
tonyb#news to me23:37
dhellmannthat's the error tellesnobrega ran into: these projects don't exist yet, and we're trying to enforce that they do23:38
dhellmannok, it's dinner time here now, so I'm going to drop offline. Feel free to take those patches over if they're broken somehow23:38
tonybdhellmann: enjoy23:38
openstackgerritMerged openstack/releases master: python-neutronclient 6.12.0 (Stein)
openstackgerritMerged openstack/releases master: Release 1.32.0 of os-client-config
openstackgerritMerged openstack/releases master: Release 1.31.0 of shade
openstackgerritMerged openstack/releases master: cliff 2.14.1
openstackgerritEric Fried proposed openstack/releases master: Release os-brick 2.8.0
smcginnisBack. Thanks for getting those done dhellmann23:59

Generated by 2.15.3 by Marius Gedminas - find it at!