Tuesday, 2018-08-07

*** frankwang has joined #openstack-release00:17
*** zhurong has joined #openstack-release00:23
*** harlowja has quit IRC00:26
*** bobh has quit IRC00:28
*** v12aml has quit IRC00:32
*** frankwang has quit IRC00:42
*** v12aml has joined #openstack-release00:47
*** hongbin has joined #openstack-release01:03
*** mriedem has quit IRC01:15
*** zhurong has quit IRC01:26
*** ricolin has joined #openstack-release01:29
*** bobh has joined #openstack-release02:13
*** lbragstad has quit IRC02:18
*** bobh has quit IRC02:34
openstackgerritzhurong proposed openstack/releases master: Release solum-dashboard 2.4.1 and cut stable/rocky  https://review.openstack.org/58887902:47
openstackgerritLingxian Kong proposed openstack/releases master: Release python-qinlingclient 2.1.0 and create stable/rocky  https://review.openstack.org/58932802:52
openstackgerritLingxian Kong proposed openstack/releases master: Qinling RC1 and create stable/rocky  https://review.openstack.org/58932902:53
openstackgerritzhurong proposed openstack/releases master: Release solum-dashboard 2.5.0 and cut stable/rocky  https://review.openstack.org/58887902:53
*** rosmaita has quit IRC03:13
*** jhesketh_ is now known as jhesketh03:14
openstackgerritLingxian Kong proposed openstack/releases master: Qinling RC1 and create stable/rocky  https://review.openstack.org/58932903:31
*** dave-mccowan has quit IRC03:31
*** udesale has joined #openstack-release03:48
openstackgerritLingxian Kong proposed openstack/releases master: Qinling RC1 and create stable/rocky  https://review.openstack.org/58932903:52
openstackgerritXueFeng Liu proposed openstack/releases master: Release senlin 6.0.0 and cut stable/rocky  https://review.openstack.org/58888904:11
*** hongbin has quit IRC04:15
openstackgerritXueFeng Liu proposed openstack/releases master: Release senlin-dashboard 0.9.0 and cut stable/rocky  https://review.openstack.org/58889104:17
openstackgerritXueFeng Liu proposed openstack/releases master: Release senlin 6.0.0 and cut stable/rocky  https://review.openstack.org/58888904:24
*** ykarel has joined #openstack-release04:35
*** e0ne has joined #openstack-release05:00
*** e0ne has quit IRC05:58
*** e0ne has joined #openstack-release06:02
*** ifat_afek has joined #openstack-release06:16
*** egonzalez has joined #openstack-release06:28
*** pcaruana has joined #openstack-release06:36
*** e0ne has quit IRC07:02
*** amoralej|off is now known as amoralej07:08
*** e0ne has joined #openstack-release07:35
*** e0ne has quit IRC07:41
*** ykarel is now known as ykarel|lunch07:43
*** jpich has joined #openstack-release07:45
*** e0ne has joined #openstack-release07:53
*** e0ne has quit IRC07:53
*** AJaeger has left #openstack-release08:11
*** electrofelix has joined #openstack-release08:33
*** ykarel|lunch is now known as ykarel08:35
*** huats has joined #openstack-release09:30
*** finucannot is now known as stephenfin09:30
*** electrofelix has quit IRC10:18
*** olivierbourdon38 has joined #openstack-release10:26
*** electrofelix has joined #openstack-release10:26
*** dave-mccowan has joined #openstack-release10:51
*** ricolin has quit IRC10:58
*** udesale has quit IRC11:15
openstackgerritJean-Philippe Evrard proposed openstack/releases master: [DNM] Test separating roles from the rest of OSA  https://review.openstack.org/58943311:32
*** zul has joined #openstack-release11:54
*** edmondsw has joined #openstack-release12:04
*** amoralej is now known as amoralej|lunch12:15
openstackgerritMonty Taylor proposed openstack/releases master: Release 0.17.2 of openstacksdk  https://review.openstack.org/58945112:32
*** ifat_afek has quit IRC12:34
mordredsmcginnis, dhellmann, ttx, prometheanfire: ^^ I sent an FFE to the mailing list, but tl;dr bugfix release for a bug affecting nodepool. the bug has no impact on the rest of openstack12:38
*** e0ne has joined #openstack-release12:40
*** weshay has quit IRC12:50
*** tellesnobrega has quit IRC12:50
openstackgerritMonty Taylor proposed openstack/releases master: Release 1.3.0 of os-service-types  https://review.openstack.org/58921912:51
*** bobh has joined #openstack-release12:54
*** egonzalez has quit IRC12:59
ttxmordred: not sure we need an FFE for a bugfix release but thanks for the heads-up13:16
*** mriedem has joined #openstack-release13:16
*** ykarel is now known as ykarel|away13:21
mordredttx: figured it was better to have it and not need it than need it and not have it :)13:23
ttxyou know us well13:24
dhellmannttx: the requirements team has been asking for FFEs to update constraints during the freeze period13:25
ttxin that case I'm not sure the constraints would be updated ?13:25
*** ykarel|away has quit IRC13:31
*** amoralej|lunch is now known as amoralej13:32
dhellmannI'm not sure. It sounds like they don't need to be, but if we don't then we end up in a weird state after we branch requirements13:36
dhellmannwhere we have a stable/rocky release that isn't being used in the tests13:36
openstackgerritMonty Taylor proposed openstack/releases master: Release 1.3.0 of os-service-types  https://review.openstack.org/58921913:41
ttxack13:52
smcginnisYeah, it should at least update u-c I would think.14:04
dhellmannqinling was late for their client library deadline, but early for the rc1, so I guess that averages out ok, right?14:10
smcginnisHah, sure. :)14:11
*** jrist has quit IRC14:15
openstackgerritMerged openstack/releases master: Release solum-dashboard 2.5.0 and cut stable/rocky  https://review.openstack.org/58887914:19
openstackgerritMerged openstack/releases master: Qinling RC1 and create stable/rocky  https://review.openstack.org/58932914:23
openstackgerritMerged openstack/releases master: Release senlin 6.0.0 and cut stable/rocky  https://review.openstack.org/58888914:23
openstackgerritXueFeng Liu proposed openstack/releases master: Release senlin-dashboard 0.9.0 and cut stable/rocky  https://review.openstack.org/58889114:23
*** rpioso|afk is now known as rpioso14:26
*** jrist has joined #openstack-release14:27
evrardjpdo we have an idea on how hard would it be (and if that would be allowed) to have a text file (manifest) as release artifact14:36
evrardjpI'd like to say: When releasing openstack-ansible sha x, we fetch a file from gate logs corresponding to testing of said sha x, and publish that file.14:37
*** ykarel has joined #openstack-release14:38
*** hongbin has joined #openstack-release14:38
dhellmannevrardjp : what would be in the file? a list of the files in the release?14:38
evrardjpsomething like this: https://github.com/openstack/openstack-ansible/blob/stable/queens/ansible-role-requirements.yml14:39
evrardjpbasically a manifest of what to download, so more shas.14:39
dhellmannah14:39
smcginnisWe could probably have a special release job?14:39
dhellmannthat would be in addition to the tarball? or inside the tarball?14:39
*** e0ne has quit IRC14:39
evrardjpdhellmann: we don't publish a tarball14:40
dhellmannoh, is the tag operation a no-op? or does it just do something different?14:40
evrardjpit tags the repos14:40
evrardjpnot so sure to understand14:40
evrardjpsmcginnis: yeah that would be a special job I guess14:40
dhellmannwhat happens when we tag one of these repositories?14:40
dhellmannwhat is being published now, and to where?14:41
dhellmannand how is that dependency list managed today? is it checked in to the git repository?14:41
evrardjpso now, when OSA requests a release, we simply give the sha to use, and it gets tagged. Then it's published on the generic releases pages, but no artifact attached14:41
smcginnisevrardjp: I do see a few ansible-* publishing to http://tarballs.openstack.org/14:41
evrardjpsee for example: https://releases.openstack.org/queens/index.html#openstack-ansible14:42
evrardjpsmcginnis: that's triple-o's14:42
* smcginnis is surprised by the number of project names he doesn't recognize on http://tarballs.openstack.org/14:42
smcginnisevrardjp: Ah14:42
dhellmannand how is that requirements file being managed?14:42
evrardjpdhellmann: manually by the ptl14:43
evrardjpwith my own tooling.14:43
dhellmannok, so a job that published that file would be able to find it in git14:43
evrardjpwell14:43
evrardjpno I'd like to change that14:43
evrardjpI said a file "like" <link>14:43
dhellmannso that is not a list of things that have been tested together?14:43
evrardjplet me rephrase. Right now it is: When we tag, we have that ansible role requirement files manifest in14:44
evrardjpbaked in the code14:44
evrardjpso someone consuming a tag of "openstack-ansible" will know which roles tag to consume, because it's part of the a-r-r file.14:44
dhellmannthat seems nice and tidy14:45
evrardjpthat's fine for now, but it means things to bump on a regular basis, and it's what basically made us miss last deadline14:45
evrardjpbecause of timeout issues, the change of SHAs of this file couldn't pass14:45
dhellmannok14:45
evrardjpso as this is maintenance burden I thought of another way to do it14:45
*** annabelleB has joined #openstack-release14:46
evrardjpinside openstack-ansible we'll simply consume an "artifact", which is similar to the ansible-role-requirement file, but it will be out of tree:14:46
evrardjpthis artifact will be something we publish on tarballs or releases.openstack.org14:46
dhellmannok, so if we had a job that did that, where would it get the information to put into the file?14:47
evrardjpthat would be from the gate logs14:47
evrardjpOSA gate logs14:47
evrardjpnot releases gate logs14:47
dhellmannand how would the information end up in the gate logs?14:47
dhellmannit sounds like you're talking about giving up control over which versions you test with in order to not have to manage a file that gives you that control14:48
evrardjpso in our OSA gates, we'd prepare the artifact file.14:48
evrardjpyes and no14:48
evrardjpthe file gives the control of what code we run indeed. But what's tested is what is tested, so if we have an artifact of what's tested, we have reproducibility14:49
dhellmannbut no control, right? this is the problem we fought for so long with the global requirements list, and solved with the constraints list14:49
evrardjpI am not sure what you really mean by no control, but yeah, it would be automatic14:50
evrardjpnobody should care about this14:51
dhellmannit sounds like there are 2 modes here14:51
evrardjpI simplify things, there are more than 2 modes in fact.14:51
dhellmannin the current mode, you manually edit a file, and that file controls which SHAs of each playbook or dependency are used in the tests14:52
evrardjpcorrect14:52
dhellmannin the mode I think you are proposing, the file would not have SHAs and so you would not be able to control which versions of those things are used14:52
dhellmannis that interpretation correct?14:52
evrardjppartially14:52
dhellmannhow "partially"? :-)14:52
evrardjpI am trying to phrase this with proper english sorry if it takes time :)14:53
evrardjpto consume this file we are talking about we have a script.14:53
dhellmannbien sur, c'est bon14:53
evrardjpthat script would alter his behavior on two parts: the default would be to consume the public artifact14:53
evrardjpdhellmann: :)14:53
evrardjpthe non default would be to override this with HEAD of branch for all those roles.14:54
dhellmannah14:54
dhellmannso you would have control over some versions, but not all of them, based on what you need14:54
evrardjpgates would run non-default14:54
evrardjpexactly14:54
dhellmannok, that makes sense now14:55
evrardjpwhence "partial"14:55
evrardjp:D14:55
dhellmannunfortunately, we can't be sure that any artifact produced by a gate job is available to be published by a release job14:55
dhellmannwe could, however, have the release job compute the current values14:55
evrardjpyou mean that 15 days deadline?14:55
evrardjpor 30 days14:55
dhellmannof course, those might not be the same as what was tested14:55
evrardjpI can't remember14:55
evrardjpbut you mean expiry time of logs would prevent fetching artifacts14:56
dhellmannyes, the logs are removed after some time (or indeed when the filesystem becomes corrupted)14:56
dhellmannright; we don't want to couple the release job to the gate job for that reason14:56
*** bobh has quit IRC14:56
evrardjpthat is fair, but the volume of logs would be enough I think -- we could even think of only doing with last successful periodic14:56
*** ykarel has quit IRC14:57
evrardjpI am not sure how we would compute the values and be sure things were tested together.14:57
*** rosmaita has joined #openstack-release14:57
dhellmannyes, that would be a problem14:57
dhellmannI will have to give this more thought to come up with something14:58
dhellmannhave you talked to the infra team, yet? they may have already dealt with a similar case14:58
evrardjpI understand why it would be a problem as post job to rely on gates, but as part of the job, would that be a hard problem?14:58
evrardjpI haven't , but I will.14:59
dhellmannI think we could predict where to look for the file, so that part isn't a problem14:59
dhellmannthe problem is that the file might not be there14:59
dhellmannespecially for a merged patch, since we can't re-check that14:59
dhellmannone alternative would be to use a periodic job that proposed updates to the file15:00
dhellmannyou could have a flag on some items that controls whether those entries are updated manually or automatically15:00
dhellmannand a periodic job could propose a patch to update it, after running tests15:01
dhellmannthat would make it similar to the upper-constraints.txt file15:01
evrardjpthat's fairly true.15:01
evrardjp:)15:01
dhellmannthat would keep you from having to update it by hand, and also prevent bad shas from making it into the file15:01
evrardjpSimple, with precedent, and less code involved.15:01
dhellmannyou wouldn't have to change your existing gate job, since it could just use the shas in the file15:01
dhellmannyou would just need the new periodic job15:02
evrardjpI planned to do a periodic job to update things, but it's not what I planned, I kinda like the twist you add to it :)15:02
evrardjpseparating problem domains into small pieces always makes the system easier to improve :D15:02
dhellmann++15:03
evrardjplet me think of that, that sounds nice :)15:03
dhellmann\o/15:03
evrardjpthanks!15:03
*** mriedem is now known as mriedem_afk15:06
*** pcaruana has quit IRC15:11
*** bobh has joined #openstack-release15:17
*** bobh has quit IRC15:17
openstackgerritMerged openstack/releases master: Release 0.17.2 of openstacksdk  https://review.openstack.org/58945115:35
evrardjpI am thinking of the requirements process, it proposes a new patch, which would still need to get gated, and therefore still isn't the best solution -- I don't see a way to bypass this15:42
evrardjplet's see what infra will tell us15:43
*** bobh has joined #openstack-release15:45
dhellmannevrardjp : yes, that approach would only change the need for you to manage the file by hand15:45
dhellmannI still think you want those changes to be gated15:46
*** olivierbourdon38 has quit IRC15:46
evrardjpbut if we revert the order and publish artifact from an existing run that would merge, that would have been gated already :)15:48
evrardjpit wouldn't require a new run with same versions15:49
evrardjpwhich is good for ensuring things, but bad in terms of electrons.15:49
dhellmannsimilarly, if you land a change to that file without any tests running you can break your ability to land any other patches15:49
dhellmannmeh, we have plenty of capacity for test jobs15:49
*** onovy has quit IRC16:01
*** armstrong has joined #openstack-release16:02
*** onovy has joined #openstack-release16:08
*** mriedem_afk has quit IRC16:11
*** annabelleB has quit IRC16:17
*** annabelleB has joined #openstack-release16:18
*** e0ne has joined #openstack-release16:18
*** armax has joined #openstack-release16:19
*** amoralej is now known as amoralej|off16:21
*** jpich has quit IRC16:27
*** electrofelix has quit IRC16:29
openstackgerritAndrey Kurilin proposed openstack/releases master: [rally] Update a list of existing releases  https://review.openstack.org/58954416:41
openstackgerritAndrey Kurilin proposed openstack/releases master: [rally] Release 1.1.0 version  https://review.openstack.org/58954516:41
*** armstrong has quit IRC17:02
*** e0ne has quit IRC17:20
*** e0ne has joined #openstack-release17:21
*** e0ne has quit IRC17:22
*** ricolin has joined #openstack-release17:30
*** harlowja has joined #openstack-release17:31
*** annabelleB has quit IRC17:38
*** harlowja has quit IRC17:43
*** annabelleB has joined #openstack-release17:45
*** annabelleB has quit IRC17:55
*** annabelleB has joined #openstack-release18:01
*** e0ne has joined #openstack-release18:04
*** ricolin has quit IRC18:27
*** AJaeger has joined #openstack-release18:48
AJaegerrelease team, can you +2A stable/rocky changes? Would love to have a +2A on https://review.openstack.org/589564 for solum-dashboard to fix zuul jobs18:48
smcginnisLooks like I do not have +2 on that.18:49
dhellmannAJaeger : I don't have +2 on that stable branch, which is odd18:49
*** openstackgerrit has quit IRC18:49
dhellmannthe ACLs for that repo must not include the release managers18:49
smcginnisI've noticed I have +2 on some and not others.18:49
dhellmannmaybe it's the way those stable teams are set up? maybe the global stable team isn't listed?18:50
AJaegerdhellmann, smcginnis, solum-dashboard misses the "refs/heads/stable/" section that others have.18:51
smcginnisLooks like they don't have a separate stable core team.18:51
AJaegerexactly, they don't ...18:51
AJaegerok, let's wait for them to review - thanks for checking!18:51
smcginnisMaybe that's another thing we should add to a checklist for newly governed projects.18:52
dhellmannand/or to ttx's acl fixer script18:53
*** annabelleB has quit IRC18:54
*** bobh has quit IRC19:01
*** bobh has joined #openstack-release19:18
*** bobh has quit IRC19:23
*** mriedem has joined #openstack-release19:24
*** e0ne has quit IRC19:32
*** openstackgerrit has joined #openstack-release19:46
openstackgerritMerged openstack/releases master: Release 1.3.0 of os-service-types  https://review.openstack.org/58921919:46
openstackgerritMerged openstack/releases master: [rally] Update a list of existing releases  https://review.openstack.org/58954419:46
openstackgerritMerged openstack/releases master: [rally] Release 1.1.0 version  https://review.openstack.org/58954519:46
openstackgerritJay Bryant proposed openstack/releases master: Add Cinder Rocky Release Highlights  https://review.openstack.org/58957719:49
*** bobh has joined #openstack-release19:59
*** ifat_afek has joined #openstack-release19:59
smcginnisjungleboyj: Those should ideally be 3-5 key highlights that you want marketing type folks to know.20:00
smcginnisjungleboyj: Things like "Addition of developer reference..." I don't think really fit.20:00
*** ifat_afek has quit IRC20:01
*** AJaeger has left #openstack-release20:09
jungleboyjsmcginnis:  Ok.  I can update.20:12
smcginnisThanks!20:12
jungleboyjnit pick nit pick.  ;-)20:13
smcginnis:)20:13
*** zul has quit IRC20:13
openstackgerritJay Bryant proposed openstack/releases master: Add Cinder Rocky Release Highlights  https://review.openstack.org/58957720:15
jungleboyjsmcginnis:  How do those look?20:15
smcginnisjungleboyj: Some comments there.20:20
jungleboyjLooking.20:20
jungleboyjsmcginnis:  So are you wanting less technical descriptions?20:25
smcginnisjungleboyj: Yeah, these are high level things for marketing types to promote new improvements or features. Some of those are too low level for that kind of audience.20:26
jungleboyjHmmmm.  Ok.  It doesn't seem that different from what I had for queens.  Maybe I will try to word these  less technically?20:29
*** annabelleB has joined #openstack-release20:30
smcginnisYeah, queens wasn't great either. :P20:30
jungleboyj:-p20:31
smcginnisjungleboyj: Maybe ask "why do I care" about each thing and use the answer to that as what gets put as the highlight.20:31
jungleboyjOk.  Let me try that.20:31
EmilienMrelease-managers: can someone approve my release patches? thanks https://review.openstack.org/#/q/project:openstack/releases+owner:%22Emilien+Macchi+%253Cemilien%2540redhat.com%253E%22+status:open20:34
smcginnisEmilienM: I'll do that now. Was waiting to see if stable wanted reviews even though they aren't stable:follows-policy, but they should be good.20:35
EmilienMsmcginnis: well i'm doing the same thing every 2 weeks20:35
EmilienMnot sure what we're waiting at :D20:35
corvushi, i just performed a zuul scheduler restart with 3 items in the release-post pipeline.  they had all completed the tag-release job, but had not completed publish-static.  do i need to perform any corrective action?20:37
corvussorry for the timing -- it was an urgent fix, and zuul hasn't been giving us a lot of opportunities today to minimize the impact20:38
smcginniscorvus: Hmm, we may need to reenqueue those.20:42
-openstackstatus- NOTICE: Due to a bug, Zuul has been unable to report on cherry-picked changes over the last 24 hours. This has now been fixed; if you encounter a cherry-picked change missing its results (or was unable to merge), please recheck now.20:43
corvushttps://git.openstack.org/cgit/openstack/releases/commit/?id=e7587db1a001450f18d38aa0503aa53f14d34be420:44
corvushttps://git.openstack.org/cgit/openstack/releases/commit/?id=735e7eee606a54559b1bfca5464dc62632e8591320:44
corvushttps://git.openstack.org/cgit/openstack/releases/commit/?id=157213d54a5ce58f320638db88d749947bab4bc020:44
corvusthose were the 3 in the pipeline20:44
smcginniscorvus: https://git.openstack.org/cgit/openstack/releases/commit/?id=735e7eee606a54559b1bfca5464dc62632e85913 can probably be skipped, but it looks like the other two did not complete everything.20:46
corvuswhat does publish-static do?20:47
smcginnisThat's just for the docs I believe, but doesn't look like the others finished publishing to pypi and such.20:50
corvusoh, of course the tag-release job is just going to create the tag; the actual release would be elsewhere20:51
corvushttp://git.openstack.org/cgit/openstack/os-service-types/refs/20:53
corvusthat got the tag applied20:53
corvusi didn't see anything in the release pipeline though20:54
corvushrm.  i do see entries for it in the log20:54
corvusi guess i missed them on the status page20:55
corvus <Tag 0x7f96db092080 openstack/os-service-types creates refs/tags/1.3.0 on d05997a1f416159c948ca4ff2b60e07336a998e4>20:55
corvus<Tag 0x7f96d8874160 openstack/rally creates refs/tags/1.1.0 on 0cd69c70492f800e0835da4de006fc292e43a5f1>20:55
corvusthat's the contents of the release pipeline20:55
corvussmcginnis: that agrees with what you found20:56
corvuszuul enqueue-ref --tenant openstack --trigger gerrit --pipeline release --project openstack/os-service-types --ref refs/tags/1.3.0 --newrev d05997a1f416159c948ca4ff2b60e07336a998e420:57
corvuszuul enqueue-ref --tenant openstack --trigger gerrit --pipeline release --project openstack/rally --ref refs/tags/1.1.0 --newrev 0cd69c70492f800e0835da4de006fc292e43a5f120:57
corvussmcginnis, fungi: i'd appreciate a second + third pair of eyes on that20:58
smcginniscorvus: Thanks! Those look right to me, but hopefully fungi can confirm.20:59
corvusoh, right, fungi is getting sushi20:59
corvusclarkb: ^ ?21:00
smcginnisMmmm, sushi.21:00
* clarkb looks21:00
clarkbcorvus: the project, tag, ref tuples you have lgtm21:01
corvusok doing that now21:02
corvusdone21:02
smcginnisThanks corvus21:04
openstackgerritSean McGinnis proposed openstack/releases master: Add/update rocky release notes links  https://review.openstack.org/58963921:14
*** edmondsw has quit IRC21:29
*** rosmaita has quit IRC22:11
*** bobh has quit IRC22:12
*** strigazi has joined #openstack-release22:20
*** strigazi has quit IRC22:21
*** strigazi has joined #openstack-release22:21
*** strigazi has quit IRC22:27
*** strigazi has joined #openstack-release22:28
*** strigazi has quit IRC22:28
*** strigazi has joined #openstack-release22:29
*** strigazi has quit IRC22:32
*** strigazi has joined #openstack-release22:33
*** hongbin has quit IRC22:39
*** annabelleB has quit IRC22:41
*** rpioso is now known as rpioso|afk22:54
*** edmondsw has joined #openstack-release22:54
*** annabelleB has joined #openstack-release22:58
*** edmondsw has quit IRC22:59
fungisorry about that! back from sushi now23:04
fungigetting ready for close of ptl elections followed by tc office hour, so wanted to get in some eats while i had the chance23:04
prometheanfireos-service-types?23:07
prometheanfirehttps://review.openstack.org/58964423:07
dhellmannah, darn, I didn't think anything used that23:08
dhellmannI mean, I thought it was just a tool for some of our CI stuff, I didn't realize it was actually used in all of those libs23:09
dhellmannprometheanfire : it should be sufficient to update the constraints list, unless mordred knows differently23:09
mordreduhoh23:10
dhellmannit looks like only a few projects actually have a direct dependency23:10
dhellmannkeystoneauth, nova, openstacksdk23:10
mordredyah - should be a small set23:10
mordredthat sounds correct23:10
mordredand yes - u-c should be plenty - nothing should be depending on new features23:11
dhellmannthanks for confirming23:12
* dhellmann hears the dinner bell23:12
mordredbut also - it would be fine with not u-c - it's an independent release - that we're releasing it right now is unrelated to the rocky release - if rocky stuck with 1.2.0 in u-c until the end of time I don't think anything would break23:12
mordredI shall defer judgement on that concept to the fine folks here who are smarter about such things23:12
dhellmannmordred : what is the release model for the library?23:13
mordreddhellmann: independent23:13
dhellmannoh, it is, isn't it23:13
dhellmannok then23:13
dhellmannyeah, so we could hold off on the uc change if we want, prometheanfire23:13
* dhellmann really leaves for dinner this time23:13
mordreddhellmann: yeah. it's got the service-types-authority data in it, so it's intended to be treated more like tzdata23:14
prometheanfireif it's UC only that's a low bar, just needs the request23:14
prometheanfireI's and T's23:14
mordredprometheanfire: we need FFEs for independent releases too?23:14
* mordred happy to comply, mostly just learning23:14
prometheanfirefor requirements updates everything needs a FFE23:14
prometheanfirebecause it still hits projects23:15
mordredkk23:16
prometheanfirenot too much it seems https://github.com/openstack/os-service-types/compare/1.2.0...1.3.023:16
prometheanfireffe for reqs is there for a diferent but related reason as other projects23:16
mordredprometheanfire: FFE in the mail23:19
prometheanfirecoolbeans23:21
openstackgerritLingxian Kong proposed openstack/releases master: Release python-qinlingclient 2.1.0 and create stable/rocky  https://review.openstack.org/58932823:30

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