Thursday, 2019-02-28

*** sdake has joined #openstack-release00:03
*** dave-mccowan has quit IRC00:07
*** mriedem has quit IRC00:13
*** mriedem has joined #openstack-release00:19
*** lbragstad has quit IRC00:32
*** dangtrinhnt has quit IRC00:40
*** sdake has quit IRC01:08
*** dangtrinhnt has joined #openstack-release01:17
openstackgerritTony Breeds proposed openstack/releases master: Generate the constraints redirections from the deliverable data  https://review.openstack.org/63901101:31
openstackgerritTony Breeds proposed openstack/releases master: Generate the constraints redirections from the deliverable data  https://review.openstack.org/63901101:50
*** sdake has joined #openstack-release02:09
*** hongbin has joined #openstack-release02:32
*** sdake has quit IRC02:46
*** ekcs has quit IRC02:47
*** udesale has joined #openstack-release03:15
*** sdake has joined #openstack-release03:22
*** sdake has quit IRC03:23
*** sdake has joined #openstack-release03:27
*** mriedem has quit IRC03:32
*** sdake has quit IRC03:40
*** spsurya has joined #openstack-release04:14
openstackgerritdharmendra kushwaha proposed openstack/releases master: tacker-horizon stein release 0.13.0  https://review.openstack.org/63963404:18
*** ykarel|away has joined #openstack-release04:19
*** ykarel|away is now known as ykarel04:20
*** armax has quit IRC05:00
*** hongbin has quit IRC05:16
*** sdake has joined #openstack-release05:31
*** sdake has quit IRC06:02
*** sdake has joined #openstack-release06:22
*** sdake has quit IRC06:26
*** sdake has joined #openstack-release06:42
*** sdake has quit IRC07:15
*** sdake has joined #openstack-release07:18
*** sdake has quit IRC07:19
*** aojea has joined #openstack-release07:25
*** tesseract has joined #openstack-release08:00
*** jpich has joined #openstack-release08:00
*** jtomasek has joined #openstack-release08:01
openstackgerritbaisen proposed openstack/releases master: Relase tricircle for Stein  https://review.openstack.org/63994508:17
*** pcaruana has joined #openstack-release08:32
*** tosky has joined #openstack-release08:39
*** hberaud|gone is now known as hberaud08:40
*** ykarel is now known as ykarel|lunch08:43
openstackgerritAkihiro Motoki proposed openstack/releases master: release neutron-lib 1.25.0  https://review.openstack.org/63925508:55
*** jaosorior has joined #openstack-release09:06
*** electrofelix has joined #openstack-release09:11
*** sdake has joined #openstack-release09:14
*** olivierbourdon38 has joined #openstack-release09:20
*** olivierbourdon38 has quit IRC09:22
*** udesale has quit IRC09:28
*** udesale has joined #openstack-release09:29
*** e0ne has joined #openstack-release09:32
*** sdake has quit IRC09:46
*** ykarel|lunch is now known as ykarel09:48
*** dtantsur|afk is now known as dtantsur09:49
openstackgerritChris Dent proposed openstack/releases master: Release 0.3.0 of os-resource-classes  https://review.openstack.org/63997110:03
*** sohny has joined #openstack-release10:21
*** udesale has quit IRC10:24
*** udesale has joined #openstack-release10:24
*** sohny has quit IRC10:34
*** sdake has joined #openstack-release10:37
*** luizbag has joined #openstack-release10:38
*** smrcascao has quit IRC10:40
sean-k-mooneysmcginnis: tonyb o/ melanie has +1'd https://review.openstack.org/#/c/639860/ over night. when ye get online could ye take a look again.11:00
* ttx waves11:01
*** sdake has quit IRC11:18
*** sdake has joined #openstack-release11:20
*** e0ne has quit IRC11:30
*** e0ne has joined #openstack-release11:36
*** jpich has quit IRC11:47
openstackgerritJavier Peña proposed openstack/releases master: Release pymod2pkg 0.17.2  https://review.openstack.org/64001011:53
openstackgerritThomas Bechtold proposed openstack/releases master: pymod2pkg: release 0.17.2  https://review.openstack.org/64001111:53
*** sdake has quit IRC11:55
*** hberaud is now known as hberaud|lunch12:14
openstackgerritJuan Antonio Osorio Robles proposed openstack/releases master: TripleO: minor release for rocky  https://review.openstack.org/63785812:55
*** luizbag has quit IRC12:58
*** dave-mccowan has joined #openstack-release13:11
*** luizbag has joined #openstack-release13:16
dhellmannevrardjp : I was going to +2 https://review.openstack.org/#/c/639000/ (where you have a -1) and wanted to talk about your question first. Do you have a minute?13:16
*** hberaud|lunch is now known as hberaud13:27
evrardjphey13:27
evrardjpremoving my -1 first because it got attention13:27
evrardjpI am now listening13:27
dhellmannhey13:28
dhellmannI think the commit message says what you're asking it to say, but in a way that may not be clear if you don't have the background for what tonyb is doing13:28
dhellmannthe follow-up patch is the thing that needs this data, did you have time to review that?13:29
evrardjpI think I opened it and read it without leaving a comment13:29
dhellmannk13:29
evrardjpthe redirection bit, right?13:29
dhellmannyeah13:29
dhellmannthe idea is to have a URL per series for the constraints file and have that keep working after the branch is closed13:30
evrardjpplease let me check something real quick first13:30
evrardjpok understood it13:30
dhellmannalso to simplify dealing with the timing of when we change the URL in the tox.ini files13:30
evrardjpwhen I reviewed it I was in the train no pun there13:30
dhellmannhaha13:30
evrardjpI was wondering if newton was still an open branch, vs an eol tag, because I thought newton was kaput13:31
dhellmannthe newton branch of the requirements repo is still open13:31
evrardjpapparently for requirements it is not13:31
evrardjpthat explains13:31
evrardjpocata and above already have their content I guess13:31
evrardjplet me check real quick in releases13:31
dhellmannright13:31
dhellmannthere have been some issues with getting newton closed down completely13:31
evrardjpgot it13:32
dhellmannright, so this is just adding the missing data to produce enough useful redirects13:32
evrardjpok I understand the state better13:33
evrardjpbut wouldn't releases: projects requirements be enough to tag something ?13:33
dhellmanngood. It seemed like this was a case of us not filling in "the new guys" about the work in progress :-)13:33
evrardjphaha13:34
dhellmannI'm not sure what you mean?13:34
evrardjpwell I have so many questions, where to start ... :D13:34
dtantsurhi folks! is it possible to list the deliverables under a project that have the final release today?13:34
evrardjpdtantsur: there sure is a command for that13:34
openstackgerritDmitry Tantsur proposed openstack/releases master: Release metalsmith 0.11.0 and create stable/stein  https://review.openstack.org/64002813:35
evrardjpsorry I am checking if there is something in process that can help you at the same time13:36
dhellmannwe should add some docs about the commands under https://releases.openstack.org/reference/using.html13:37
dhellmannwe used to have docs in the readme, but I don't see where they moved13:38
dhellmannoh, no, that was the other repo, release-tools, where we did that13:38
evrardjpdtantsur: we do not have that documented -- I guess you could use the existing venv commands13:38
dhellmanndocumenting a bunch of useful incantations of list-deliverables would be a good project for train13:38
dtantsur++13:39
dhellmanntoday is the non-client library deadline, right?13:39
evrardjpI have a few ideas there, because I think we have multiple places to link from and to13:39
evrardjpdhellmann: yes13:39
dhellmannthat would be --type library to list-deliverables13:39
dhellmannso something like this: tox -e venv -- list-deliverables --type library --team NAME13:39
evrardjpdtantsur: you can do t-x -e venv -- list-deliverables --help to see arguments you can pass13:40
evrardjpdhellmann: shouldn't the horizon libaries also be evaluated?13:40
evrardjpI mean horizon plugins13:40
evrardjpwe discussed this13:40
evrardjpmy memory is already flushed13:40
dhellmannoh, maybe?13:41
dhellmannso add --type horizon-plugin to that command, dtantsur13:41
evrardjpahah I am not alone then13:41
openstackgerritDmitry Tantsur proposed openstack/releases master: Release ironic-lib 2.16.2 and create stable/stein  https://review.openstack.org/64002913:41
* dtantsur tries13:41
evrardjpI think we maybe decided to not have the --type horizon-plugin to do it later, but my memory is... flaky there13:41
evrardjpit's very complex for me, I need one week-end to read the whole thing, draw diagrams, and let it soak.13:42
dhellmannyeah, I could see us considering those "clients" or even leaving them to the final deadline13:42
dhellmanndo we want the stable branches created this week?13:42
evrardjpanyway, I will return to my series of questions then :p13:42
evrardjpdhellmann: that's early ?13:43
evrardjpI thought that was rc time13:43
dhellmannyes, we don't branch the services until rc113:43
dhellmannI suppose if there is feature work to be done in a  library we would want to branch it now13:43
dhellmannI would have to find smcginnis' email to see what he recommended13:44
dhellmannah, point 5 of https://releases.openstack.org/reference/process.html#final-library-release-week-before-milestone-313:44
dhellmann"allow ... do not require"13:44
evrardjpmakes sense13:45
dhellmannevrardjp : so, back to the redirect stuff?13:47
*** lbragstad has joined #openstack-release13:54
openstackgerritMerged openstack/releases master: pymod2pkg: release 0.17.2  https://review.openstack.org/64001114:03
openstackgerritMerged openstack/releases master: Release Senlin Stein b1  https://review.openstack.org/63980614:10
*** mriedem has joined #openstack-release14:13
*** ykarel has quit IRC14:15
*** smrcascao has joined #openstack-release14:15
*** ykarel has joined #openstack-release14:15
dtantsuroh, forgot to say thanks you: list-deliverables helped me14:15
openstackgerritMerged openstack/releases master: tacker-horizon stein release 0.13.0  https://review.openstack.org/63963414:17
openstackgerritMerged openstack/releases master: release os-vif 1.15.1  https://review.openstack.org/63986014:17
evrardjpdtantsur: good to hear that : )14:17
smcginnisI believe we've always treated horizon plugins and client libs. Since they are kind of clients.14:20
*** ianychoi has joined #openstack-release14:20
dhellmannthat seems right to me14:22
ttxin the past we treated them as "other" deliverables -- meaning they could be released late14:23
ttxNothing "depends" on them14:23
ttxthey are at the top of the foodchain14:23
openstackgerritColleen Murphy proposed openstack/releases master: Release keystoneauth 3.12.0  https://review.openstack.org/64004114:26
openstackgerritMerged openstack/releases master: Release cinder 11.2.0  https://review.openstack.org/63640114:27
openstackgerritColleen Murphy proposed openstack/releases master: Release keystonemiddleware 6.0.0  https://review.openstack.org/64004514:32
openstackgerritColleen Murphy proposed openstack/releases master: Release python-keystoneclient 3.19.0  https://review.openstack.org/64004714:35
smcginniscmurphy: Client lib deadline isn't until next week. Now is fine, but just making sure you're aware in case there might be more the team would want to get in.14:38
cmurphysmcginnis: we have another keystonemiddleware change that depends on the client change, we're thinking maybe we can squeeze that in today but understand if we can't14:39
cmurphyin any case getting the ci green for the ksm change would be nice14:39
smcginniscmurphy: So the non-client lib has a dependency on the client lib?14:40
cmurphysmcginnis: yes :/14:40
smcginniscmurphy: I see.14:40
openstackgerritChris Dent proposed openstack/releases master: Release 0.3.0 of os-resource-classes  https://review.openstack.org/63997114:52
*** mlavalle has joined #openstack-release14:56
evrardjpthat's a pickle15:13
*** e0ne has quit IRC15:16
*** e0ne has joined #openstack-release15:19
evrardjpI see a session called PTL tips and tricks in the denver forum planning -- is there something we should do for release in that context? Gathering feedback from ptl/release liaison just after that one would be useful.15:22
smcginnisNot a bad idea.15:24
smcginnisWe did want to try to get feedback on the changes we've made this cycle to see if they feel it's helped them or not.15:24
smcginnisMight be a good opportunity to do that.15:24
openstackgerritDmitry Tantsur proposed openstack/releases master: Release sushy 1.8.0 and create stable/stein  https://review.openstack.org/64006115:28
bnemecAs the proposer of that session I would be good with having a section for release discussion. :-)15:32
bnemecIn fact, that's sort of why I'm in this channel right now.15:32
bnemecI made a note for myself last cycle that I should make sure to release all the Oslo projects, even if they only had test-related changes.15:33
bnemecThe reason was that some of our stable branch jobs broke last time around because we branched off old commits that were missing necessary test fixes.15:33
bnemecSince this week is non-client library final releases, do I need to do that now or is there some other way to handle it?15:34
dhellmannbnemec : it seems like a good thing to do now15:37
bnemecdhellmann: Okay, thanks. I'll get that proposed ASAP.15:38
evrardjpbnemec: thanks15:38
dhellmann++15:38
*** armax has joined #openstack-release15:46
openstackgerritBen Nemec proposed openstack/releases master: Final Oslo releases for Stein  https://review.openstack.org/64007615:56
bnemecThat's a whole buncha releases.15:57
smcginnisWow, dang, that is. :)15:57
*** ykarel is now known as ykarel|away15:58
smcginnis#startmeeting releaseteam16:00
openstackMeeting started Thu Feb 28 16:00:03 2019 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
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
smcginnisPing list: smcginnis ttx dhellmann diablo_rojo hberaud evrardjp fungi armstrong16:00
smcginnis#link https://etherpad.openstack.org/p/stein-relmgt-tracking Agenda16:00
dhellmanno/16:00
fungialoha16:00
smcginnisGetting really far down in that tracking etherpad now.16:00
*** armstrong has joined #openstack-release16:00
diablo_rojoo/16:00
evrardjpo/16:01
ttxo/16:01
smcginnis#topic TripleO release issues16:02
*** openstack changes topic to "TripleO release issues (Meeting topic: releaseteam)"16:02
smcginnis#link https://review.openstack.org/#/c/63785716:02
smcginnis#link https://review.openstack.org/#/c/637858/16:02
smcginnis#link https://review.openstack.org/#/c/638459/16:02
smcginnisTasks update16:02
smcginnisOops, a little too much grabbed on that last one. :)16:02
smcginnisNot sure who added this topic.16:03
hberaudo/16:03
smcginnishttp://logs.openstack.org/57/637857/4/check/openstack-tox-validate/502eeab/job-output.txt.gz#_2019-02-22_10_12_23_71525316:03
smcginnisLooks like they need a release job defined and they have errors in their readme.16:04
evrardjpit looks like ttx might have added this?16:04
smcginnisttx: This one yours?16:04
evrardjpsee also last comments on https://review.openstack.org/#/c/63785716:04
ttxyes16:04
ttxIt looks like this pile of things are blocked16:05
ttxFirst do fail due to a validation error16:05
ttx(missing release job for instack-undercloud)16:06
ttxbut apparently fixing that is not the solution16:06
ttxsee https://review.openstack.org/#/c/638459/16:06
smcginnisI thought that was actually what was needed.16:07
ttxyeah, me too16:07
smcginnisMaybe we just need to let Andreas know that?16:07
ttxbut sending Juan Antonio falling down the cracks between our teams is not the best we can do16:07
ttx"You have everything set up to release - the release repo check just does not know ;)"16:07
smcginnishttps://github.com/openstack/tripleo-image-elements/blob/stable/queens/zuul.d/layout.yaml#L816:08
evrardjpsorry it was kinda my fault to ping then16:08
evrardjpit's been laying around so I wanted some fresh eyes :)16:08
smcginnisI didn't think we could do that in-repo due to secrets.16:08
dhellmannyeah, we require the template so we don't have to know all of the other places jobs can be attached to projects16:08
smcginnisdhellmann: Can you comment on https://review.openstack.org/#/c/638459/16:08
ttxmaybe our repo check is a bit too restrictive. Since we did have a light agenda I suggested we look into it and give them an answer :)16:08
dhellmannthe issue is that they have listed individual jobs in the release queue so ajaeger doesn't want to add the template16:08
dhellmanncommented16:09
dhellmannI also restored the patch16:09
smcginnisSo we either need to expand our validation checking for whatever combination folks try to add, or we enforce that they are consistent with how this is done.16:09
smcginnisI like consistency.16:09
ttxexpanding our validation is unfortunately not easy16:10
diablo_rojo+2 for consistency16:10
smcginnisBut, they do still need to get their README fixed too.16:10
fungianybody know the backstory on why they aren't using the template today?16:10
ttxwithout reimplementing the full Zuul logic for it16:10
fungilike is it just historical baggage or are there jobs in the template they don't want to (or can't) run?16:10
dhellmannfwiw, this hasn't been a problem since I made the decision to require using the templates at the very beginning of writing the validation16:10
smcginnisLooks like that patch could be updated to also remove the individual jobs if they are adding the template.16:10
evrardjpcouldn't the freeze job details help here?16:11
dhellmannthere are some cross-dependencies listed there. maybe those are redundant?16:11
smcginnisThose seem... odd.16:11
ttxyes, that patch should drop the individual job def16:11
fungii've lost track apparently. where are you looking at cross-dependencies?16:12
*** udesale has quit IRC16:13
dhellmannhttps://review.openstack.org/#/c/638459/1/zuul.d/projects.yaml line 4523 and below16:13
ttx"these have to dupe the publish-to-pypi jobs16:13
ttx    # because of the branch designation for the release job16:13
ttx"16:13
dhellmannnot "cross" but dependencies16:13
fungioh, i didn't think to look at context further down below the diff16:13
dhellmannajaeger's objection to the patch seemed to be that the template was redundant16:14
ttxso the duplication was intentional16:14
smcginnisWhich is valid. But our validation enforces that convention.16:14
*** dangtrinhnt has quit IRC16:15
dhellmannI suppose this wouldn't be an issue if the master branch wasn't closed?16:15
smcginnisI think that's the only gotcha in all that.16:15
*** dangtrinhnt has joined #openstack-release16:15
ttxThe issue here is that the template does not really match what they have. So we should add another template to match what they have, and add that to the validation test16:15
fungiwhy does it matter that they don't run jobs on master if they're not accepting patches for master anyway?16:16
ttxsome publish-tripleo template mabe16:16
dhellmannttx: in what way does it not match?16:16
*** e0ne has quit IRC16:16
fungidhellmann: the branch exclusions16:16
smcginnisfungi: Yeah, there won't be any releases on master, so does it really matter?16:16
dhellmannI don't see any branch exclusions in this patch, are those in the template?16:17
fungidhellmann: the lines just after the diff16:17
dhellmannthose are the check jobs16:17
dhellmannI don't see any exclusions in the release jobs16:17
ttxfungi: maybe the check/gate could stay16:17
*** dave-mccowan has quit IRC16:17
fungiyeah, those are the ones i was talking about, not the release jobs16:18
dhellmannoh, I see, those are release test jobs16:18
fungijust wondering why they even need to exclude master if they're not accepting changes for master16:18
dhellmannI suppose they had to exclude the job from master in order to close it and change the readme in the first place16:18
dhellmannthey could probably remove all of that now16:18
fungiright, cleanup16:18
dhellmannwfm16:18
evrardjpI am confused there16:19
ttxok, so remove all jobs and replace them with the template16:19
smcginnisThis is getting into zuul configuration, so confusion is normal. :)16:19
dhellmanns/normal/required/16:19
evrardjpI would hope not to me :p16:19
dhellmannhere's what I think happened:16:19
dhellmann1. one day, a long time ago, this was a normal project.16:20
evrardjpbut they don't want to run those jobs for master, which makes sense?16:20
fungievrardjp: the complexity seems to be that they've retired the instack-undercloud repo, but because it wasn't retired until the current cycle they had to leave testing in place to accept fixes on stable branches16:20
dhellmann2. they closed master to new development, but kept the stable branches open16:20
dhellmann3. to do that, they had to disable some jobs on master16:20
dhellmann4. they did that by listing them all out explicitly instead of using the template16:20
dhellmann5. now the release validation is complaining because the template is not there16:20
evrardjpbecause they would need to override per branch in step 416:20
fungiright16:21
dhellmannright16:21
fungii agree with dhellmann's probable timeline there16:21
evrardjpme too, that's my understanding16:21
evrardjpI don't understand how cleaning would help :p16:21
ttxok, should we propose the fix? Or go to write a lengthy explanation and expect someone else to push it?16:21
smcginnisSo since they are not accepting changes to master, now that they've gotten past that final merge to master there is no need to have special handling.16:21
dhellmannthe fix is to clean up the explicit job listings and apply the template16:21
dhellmannthe jobs will run on master and fail, but we don't care16:21
fungiwe're basically missing a step after retiring the master branch to put the jobs back the way they were16:21
dhellmannevrardjp : because it removes ajeager's objection to having redundant information in the config16:21
evrardjpsmcginnis:  oh ok16:21
dhellmannttx: perhaps we should do it16:22
ttx++16:22
smcginnisThis is an odd case where a repo was retired but they still care about stable.16:22
ttxI can push it if we agree16:22
dhellmannttx: ++16:22
evrardjpthanks ttx16:22
smcginnisttx: That would be great.16:22
ttx(I'll just remove lines 4506 and below)16:22
ttxthat will do it right16:22
dhellmannttx: perhaps with a nice big comment in there with the template explaining why it's ok16:22
dhellmannyes16:22
ttxI'll explain in commit message16:23
evrardjpI still believe this is not the ultimate right way, but I am not sure we have the right tools now16:23
*** e0ne has joined #openstack-release16:23
smcginnisevrardjp: What is you suggestion?16:23
dhellmannwhat would you do instead?16:23
evrardjpbut hey, we all agree :)16:23
evrardjpI have nothing for now, but I would think changing the validation to use the future zuul's freeze api would help16:24
smcginnisFuture zuul fixes everything. :)16:24
evrardjpbecause we could freeze the job info per branch, so it means for the release we are looking for we could know or not if that  job exists16:24
dhellmannperhaps. the point of using the templates was to enforce an *interface* for releasing without enforcing details that tend to change a lot16:24
evrardjpfair :)16:24
dhellmanni.e., we added test jobs to that template this cycle16:25
evrardjpin any way, that's only about the future :D16:25
ttxfungi: should I keep a noop in check nd gate pipelines?16:25
fungievrardjp: i might agree with you if we even had consensus on the patch series for those zuul features yet16:25
evrardjpsorry to digress here16:25
fungittx: nope, the noop job can go away16:25
evrardjpfungi: :D16:25
smcginnisI see they are in the process of merging a README fix, so the other issue should be resolved shortly too.16:25
dhellmannagreed16:25
smcginnisAny more on these?16:26
smcginnis#topic Tasks update16:26
fungiif they're adjusting the readme on master, then we shouldn't remove the jobs in 638459 until that's done16:26
*** openstack changes topic to "Tasks update (Meeting topic: releaseteam)"16:26
dhellmannI hope they're only adjusting it in the releasable branches?16:26
smcginnisfungi: No, master and stable/rocky are done. They just hadn't fixed queens.16:26
fungiokay, in that case it's fine16:26
smcginnisdiablo_rojo: Did you follow up with QA?16:27
diablo_rojosmcginnis, I did16:27
diablo_rojosounded like he had it handled and didn't need anything from us16:27
ttxDone @ https://review.openstack.org/#/c/638459/16:27
smcginnisdiablo_rojo: Excellent, thanks.16:27
smcginnisAnd thanks ttx16:27
diablo_rojosmcginnis, no problem :)16:28
smcginnisfungi: Any updates on signing key?16:28
smcginnisThe other task is for generating release requests for any missed c-w-i libs.16:29
fungi#link https://sks-keyservers.net/pks/lookup?op=vindex&search=0xcdc08088c3cb45a9be08332b2354069e5b504663&fingerprint=on OpenStack Infra (Train Cycle) <infra-root@openstack.org>16:29
smcginnisI can take that unless someone else want it.16:29
smcginnisfungi: Great, thanks!16:29
fungii'm waiting for it to appear on the keyservers i'm pulling from so i can attest to it16:29
fungiso hopefully later today you'll see a signature from me on it there16:30
fungibut it's already signed by the stein cycle key16:30
ttxfungi: wondering why we still need the queue defined in https://review.openstack.org/#/c/638459/ but hey I'll add it16:30
smcginnisNo one clamoring for doing generating the release patches, so I'll do it tomorrow once we're past the deadline and see what's left.16:31
fungittx: that's so the tripleo jobs all share a named change queue16:31
ttxah ok16:31
smcginnisLooking ahead to next week's tasks, same thing for generating the client libs that are missed.16:32
fungibasically anything running those (so any changes for instack-undercloud) will end up in the tripleo queue even if they don't share jobs with other projects in that queue16:32
smcginnisI've put prometheanfire down in there as a reminder for requirements freeze.16:33
dhellmannsmcginnis : perhaps we can sign up one of our new team members for that task next week, since they have more notice16:33
smcginnisdhellmann: I like that idea. :)16:33
* dhellmann looks meaningfully at evrardjp and diablo_rojo 16:33
diablo_rojoHa ha so this is just generating another list?16:34
smcginnisIt's a matter of listing what deliverables of --type=client-lib have not been released yet and generating release patches for any that have any commits.16:34
dhellmannright, not just a list but creating the patches to trigger the missing releases16:34
evrardjpdiablo_rojo: and updating the docs I would say16:34
smcginnisActually, at this point any regardless of commits as we need a stable/stein branchign point.16:34
dhellmannthere are scripts to do it all, I think, and if not we have the parts to build the scripts16:34
diablo_rojoevrardjp, maybe we can work on this together again?16:35
evrardjpI would be fine to sync with diablo_rojo on that16:35
evrardjpyeah16:35
smcginnisThe parts are there, but I never had time to start to automate it.16:35
diablo_rojoSo we can fumble through it together?16:35
diablo_rojoI think we can figure that out.16:35
evrardjpfine for me16:35
ttxAt this point it's ok to approve stein branch creations for libraries, right?16:35
evrardjpwe'll ping for validation before sending a mass change16:35
smcginnisCool, thanks. I've added your nicks to the task in the etherpad.16:35
dhellmannwe'll help if you run into trouble, too16:35
dhellmannthank you!16:35
dhellmannttx: it is, although I've been reminding folks that they can also wait to rc116:36
smcginnisIt will be a good exercise.16:36
dhellmannour docs say "allow ... but do not require" branches this week16:36
smcginnisIf they're pretty sure they are done, no reason not to branch.16:36
dhellmannyeah, it's just a trade-off about potentially having to backport changes to fix bugs16:36
smcginnisBut if there's some concern there might still be an important bug fix, branching just causes extra work at this point.16:37
ttxSince deadline is this week and we prefer not to release libs on Fridays...16:37
dhellmannright16:37
smcginnisLast task on the list is to run the aclissues checker.16:37
dhellmannthe constraints list protects us from bad releases going into the gate16:37
dhellmannat least mostly16:37
ttxI can do that, unless someone else wants to try that16:38
dhellmannthat feels like another case where it would be good to have someone "new" do it to verify the instructions16:38
smcginnisAnyone want to walk through with ttx as he does it to learn? Like maybe someone in a similar timezone?16:38
smcginnis:)16:39
ttx(subtle hint)16:39
evrardjpWow that was targetted16:39
smcginnishehe16:39
dhellmannI don't know, where is diablo_rojo this week?16:39
evrardjpI am fine with doing a session with ttx16:39
ttxI'm jetlagges so I'm currently UTC-316:39
diablo_rojodhellmann, physically? or mentall?16:39
evrardjpI think it's simply running a shell script16:39
diablo_rojo*mentally16:39
evrardjpiirc16:39
dhellmanndiablo_rojo : temporally16:39
smcginnisevrardjp: Yeah, not a complicated task, but a few things to know.16:39
diablo_rojodhellmann, in between waking up and going to take a nap16:39
dhellmann+1 for naps16:40
diablo_rojoevrardjp, we could add that to the list too and verify against each other16:40
smcginnisOK, I've put down ttx and evrardjp for that last task.16:40
diablo_rojosince we will both need to know how to do all these things anyway16:40
diablo_rojoOh16:40
* diablo_rojo shuts up16:40
smcginnisdiablo_rojo: If you can join too, that's great.16:40
diablo_rojosmcginnis, might be a good idea16:41
evrardjpthe more the merrier16:41
smcginnisJust trying to have a good transfer of knowledge where we can.16:41
dhellmann++16:41
smcginnisThe other tasks in the process doc are reminders that I've put in the countdown email.16:42
smcginnisJust need to format them into actual content.16:42
smcginnisThat should be it for tasks.16:42
*** v12aml has quit IRC16:42
smcginnis#topic Open16:42
*** openstack changes topic to "Open (Meeting topic: releaseteam)"16:42
smcginnisAnything else we should discuss in-meeting?16:43
smcginnisOK, we can get back to work then.16:43
smcginnisThanks everyone!16:43
dhellmannthere was some discussion of forum/ptg slots, how did that end up?16:43
smcginnisOh, right.16:43
*** v12aml has joined #openstack-release16:43
smcginnisbnemec: Had a topic submitted for the forum that will be a good time to try to get release change feedback from PTLs.16:44
fungithanks smcginnis!16:44
smcginnisAnyone have a link for that?16:44
bnemecI haven't actually submitted it yet.16:44
smcginnisOK. Let me know if you need anything from us, otherwise we can watch for the session and plan to be there.16:45
bnemecYeah, I was kind of waiting to submit it to see if there was interest.16:46
bnemecSince there is, I'll go ahead.16:46
smcginnis++16:46
smcginnisOK, I guess that's it. Thanks everyone for participating in the release team.16:46
smcginnis#endmeeting16:46
*** 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/"16:47
openstackMeeting ended Thu Feb 28 16:46:59 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:47
evrardjpthanks you16:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-02-28-16.00.html16:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-02-28-16.00.txt16:47
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-02-28-16.00.log.html16:47
ttxthanks!16:47
evrardjpto you*16:47
smcginnis:)16:47
evrardjpand everyone in fact :)16:47
diablo_rojoThanks smcginnis :)16:48
smcginnisOh, wanted to remind everyone to please take a look at the proposed Train schedule I put up and see if it is sane.16:48
*** dtantsur is now known as dtantsur|afk16:55
openstackgerritMerged openstack/releases master: Release metalsmith 0.11.0 and create stable/stein  https://review.openstack.org/64002816:57
openstackgerritMerged openstack/releases master: Release ironic-lib 2.16.2 and create stable/stein  https://review.openstack.org/64002916:57
openstackgerritMerged openstack/releases master: Release keystoneauth 3.12.0  https://review.openstack.org/64004116:59
openstackgerritMerged openstack/releases master: release neutron-lib 1.25.0  https://review.openstack.org/63925516:59
*** electrofelix has quit IRC16:59
*** e0ne has quit IRC17:05
openstackgerritAbhishek Kekane proposed openstack/releases master: Release glance_store 1.0.0  https://review.openstack.org/64010317:06
*** ykarel|away has quit IRC17:09
*** luizbag has quit IRC17:16
*** luizbag has joined #openstack-release17:16
openstackgerritErno Kuvaja proposed openstack/releases master: Release glance_store 1.0.0  https://review.openstack.org/64010317:38
openstackgerritErno Kuvaja proposed openstack/releases master: Release glance_store 0.28.0  https://review.openstack.org/64010317:41
openstackgerritMerged openstack/releases master: Release 0.3.0 of os-resource-classes  https://review.openstack.org/63997117:46
openstackgerritMerged openstack/releases master: Final Oslo releases for Stein  https://review.openstack.org/64007617:52
openstackgerritMerged openstack/releases master: Release keystonemiddleware 6.0.0  https://review.openstack.org/64004517:53
*** luizbag has quit IRC17:56
openstackgerritMerged openstack/releases master: Release sushy 1.8.0 and create stable/stein  https://review.openstack.org/64006117:59
openstackgerritMerged openstack/releases master: Release python-keystoneclient 3.19.0  https://review.openstack.org/64004718:03
openstackgerritAndrey Kurilin proposed openstack/releases master: [rally] Release 1.4.1  https://review.openstack.org/64013418:06
*** aojea has quit IRC18:10
*** ykarel|away has joined #openstack-release18:16
prometheanfiresmcginnis: sorry, meeting...18:24
prometheanfiresmcginnis: action needed or just your countdown email?18:24
*** sdake has joined #openstack-release18:45
*** armstrong has quit IRC18:50
*** e0ne has joined #openstack-release18:51
*** hberaud is now known as hberaud|gone18:56
*** luizbag has joined #openstack-release18:57
*** ykarel|away has quit IRC19:01
*** luizbag_ has joined #openstack-release19:02
*** e0ne has quit IRC19:03
*** luizbag has quit IRC19:04
smcginnisprometheanfire: I was just bringing up the task from bullet 2 in our release process for milestone-319:13
smcginnishttps://releases.openstack.org/reference/process.html#milestone-319:13
prometheanfireah, k19:13
*** pcaruana has quit IRC19:14
smcginnisprometheanfire: Just let us know if there's any other requirements related things the release team needs to be aware of.19:14
prometheanfireatm no19:15
*** jtomasek has quit IRC19:16
*** whoami-rajat has quit IRC19:20
openstackgerritSean McGinnis proposed openstack/releases master: Release glance_store 0.28.0  https://review.openstack.org/64010320:07
*** sdake has quit IRC20:07
*** jtomasek has joined #openstack-release20:11
*** luizbag_ has quit IRC20:13
*** e0ne has joined #openstack-release20:16
*** tesseract has quit IRC20:22
fungithe train release signing key is showing a signature by me now: https://sks-keyservers.net/pks/lookup?op=vindex&search=0xcdc08088c3cb45a9be08332b2354069e5b504663&fingerprint=on20:26
openstackgerritMerged openstack/releases master: Release glance_store 0.28.0  https://review.openstack.org/64010320:31
*** sdake has joined #openstack-release21:03
*** dave-mccowan has joined #openstack-release21:11
*** e0ne has quit IRC21:19
*** dave-mccowan has quit IRC21:22
*** sdake has quit IRC21:23
*** sdake has joined #openstack-release21:25
*** jtomasek has quit IRC21:42
*** e0ne has joined #openstack-release21:42
*** e0ne has quit IRC21:44
*** e0ne has joined #openstack-release21:45
*** zul has quit IRC21:53
*** e0ne has quit IRC22:01
openstackgerritMonty Taylor proposed openstack/releases master: Release 0.25.0 of openstacksdk  https://review.openstack.org/64020222:04
*** sdake has quit IRC22:13
lbragstadsmcginnis what's the deadline for proposing libraries?22:24
lbragstadwe have one patch from mordred we want to get into keystoneauth before cutting another release for it22:25
smcginnisNon-client lib deadline is today. How far along is that fix?22:26
mordredsmcginnis: it was green, we just pushed up a rev to fix a review comment - but it should be clear to land as long as zuul is friendly22:28
smcginnismordred: Awesome. Gate doesn't seem too backed up, so hopefully that shouldn't take long to get through.22:29
mordredsmcginnis: fingers crossed22:29
openstackgerritMerged openstack/releases master: [rally] Release 1.4.1  https://review.openstack.org/64013422:29
openstackgerritWitold Bedyk proposed openstack/releases master: Release monasca-common 2.13.0  https://review.openstack.org/64020622:35
openstackgerritMerged openstack/releases master: Release 0.25.0 of openstacksdk  https://review.openstack.org/64020222:37
openstackgerritWitold Bedyk proposed openstack/releases master: Release monasca-statsd 1.11.0  https://review.openstack.org/64020822:39
dtroyerso question I really should know the answer to but I'm comming up blank… the sha in a release record should not be a merge commit?23:04
clarkbdtroyer: not a release team member but a merge commit should be fine since you may have to tag/release the result of a merge23:06
dtroyerclarkb: thanks, for some reason I had a doubt about that…23:06
openstackgerritDean Troyer proposed openstack/releases master: Release osc-lib 1.12.1  https://review.openstack.org/64022023:07
*** armstrong has joined #openstack-release23:23
*** armstrong has quit IRC23:35

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