Wednesday, 2018-08-15

*** hongbin has joined #openstack-release00:44
*** mriedem has joined #openstack-release00:45
mriedemsmcginnis: dhellmann: we got https://review.openstack.org/#/c/591129/ on master - we're doing an rc2 so should we backport that?00:45
* mriedem asks in #openstack-i18n00:45
mriedemnvm got my ansnwer01:00
*** mriedem has left #openstack-release01:00
*** njohnston_ is now known as njohnston01:56
*** ekcs has quit IRC02:02
*** ricolin has joined #openstack-release02:19
*** openstack has joined #openstack-release02:33
*** ChanServ sets mode: +o openstack02:33
openstackgerritHongbin Lu proposed openstack/releases master: Release Zun-ui 2.0.0 and cut stable branch  https://review.openstack.org/59188902:53
*** bobh has quit IRC03:05
*** bobh has joined #openstack-release03:10
*** bobh has quit IRC03:19
*** hongbin has quit IRC03:23
*** hongbin has joined #openstack-release03:28
*** armax has quit IRC03:34
*** hongbin_ has joined #openstack-release03:48
*** hongbin has quit IRC03:50
*** njohnston has quit IRC04:02
*** hongbin_ has quit IRC04:14
*** samP has joined #openstack-release04:19
*** oanson has quit IRC04:33
openstackgerritdharmendra kushwaha proposed openstack/releases master: Tacker: release Tacker server rocky 0.10.0rc1  https://review.openstack.org/59189204:47
*** oanson has joined #openstack-release05:00
openstackgerritMichael Johnson proposed openstack/releases master: Tag Rocky release of octavia-tempest-plugin  https://review.openstack.org/59178005:02
openstackgerritdharmendra kushwaha proposed openstack/releases master: Tacker: release Tacker server rocky 0.10.0rc1  https://review.openstack.org/59189205:05
*** pcaruana has joined #openstack-release05:12
openstackgerritdharmendra kushwaha proposed openstack/releases master: tacker-horizon rocky release 0.12.0  https://review.openstack.org/59190005:42
*** e0ne has joined #openstack-release06:16
*** alexchadin has joined #openstack-release06:59
openstackgerritAlexander Chadin proposed openstack/releases master: Add cycle-highlights to Watcher Rocky  https://review.openstack.org/59132507:32
*** electrofelix has joined #openstack-release07:40
*** jpich has joined #openstack-release07:41
*** dkushwaha has joined #openstack-release08:06
*** dtantsur|afk is now known as dtantsur08:26
*** lennyb has joined #openstack-release08:37
*** dkushwaha has quit IRC08:40
*** alexchadin has quit IRC09:00
*** samueldmq_ has joined #openstack-release09:16
*** andreaf has quit IRC09:16
*** andreaf has joined #openstack-release09:17
*** alexchadin has joined #openstack-release09:17
*** dirk_ has joined #openstack-release09:18
*** dirk has quit IRC09:18
*** samueldmq has quit IRC09:18
*** samueldmq_ is now known as samueldmq09:18
*** dirk_ is now known as dirk09:18
*** ricolin has quit IRC09:29
*** dave-mccowan has joined #openstack-release10:12
*** olivierbourdon38 has joined #openstack-release10:31
*** alexchadin has quit IRC10:59
*** alexchadin has joined #openstack-release11:00
*** alexchadin has quit IRC11:00
*** alexchadin has joined #openstack-release11:01
*** alexchadin has quit IRC11:01
*** alexchadin has joined #openstack-release11:01
*** alexchadin has quit IRC11:02
*** ricolin has joined #openstack-release11:20
*** alexchadin has joined #openstack-release11:33
*** alexchadin has quit IRC11:38
*** olivierbourdon38 has quit IRC11:55
*** alexchadin has joined #openstack-release11:56
*** rosmaita has joined #openstack-release11:57
*** bobh has joined #openstack-release11:57
*** bobh has quit IRC12:03
*** bobh has joined #openstack-release12:09
*** bobh has quit IRC12:13
*** gcb_ has joined #openstack-release12:19
*** alexchadin has quit IRC12:23
*** alexchadin has joined #openstack-release12:30
*** bobh has joined #openstack-release12:32
openstackgerritMerged openstack/releases master: Cut stable/rocky branch for devstack-plugin-container  https://review.openstack.org/59180412:32
*** pkovar has joined #openstack-release12:35
openstackgerritMerged openstack/releases master: Release osc-lib 1.11.1 (Rocky)  https://review.openstack.org/59155612:37
*** ykarel has joined #openstack-release12:37
*** ykarel is now known as ykarel|away12:49
dhellmann melwitt : ah, good12:55
smcginnisIt is a bit confusing that translations are going into master (stein) and not rocky as we are finalizing that release.12:55
dhellmannwe should probably talk with the i18n team about that. I imagine it has something to do with how easy it is to configure zanata12:56
*** ykarel|away has quit IRC13:17
*** luizbag has joined #openstack-release13:29
*** luizbag has quit IRC13:30
dhellmannsmcginnis : are we all clear for tagging and branching? It looks like we have 2-3 we could send through.13:44
dhellmannI'm assuming we want to hold off on the requirements branch for now13:44
*** annabelleB has joined #openstack-release13:55
smcginnisdhellmann: Yep, I believe we are clear to go. Let's check with Matt when he actually wants to proceed with requirements.14:08
openstackgerritMerged openstack/releases master: Add cycle-highlights to Watcher Rocky  https://review.openstack.org/59132514:20
annabelleBdhellmann smcginnis: Instead of the usual “marketing preview” for Rocky, we were thinking of just having one big community meeting open to anyone—might try to get a few PTLs to talk about their work too. Unfortunately 8am on the 30th is the most available time. Any reason that that’s a terrible time?14:29
smcginnisannabelleB: What time zone? That would really be the only challenge I see. No time is going to work well for everyone.14:32
annabelleBsmcginnis: whoops, sorry, yes, 8am pacific14:32
*** alexchadin has quit IRC14:32
*** armax has joined #openstack-release14:49
*** d0ugal has joined #openstack-release14:58
*** annabelleB has quit IRC14:59
*** annabelleB has joined #openstack-release15:07
*** rpioso|afk is now known as rpioso15:08
*** masayukig has joined #openstack-release15:10
e0nehi team. does anybody know when we'll have stable/rocky in the openstack/requirements project?15:24
e0nehorizon needs if for rc215:26
prometheanfireI'll need to update the sha for the reqs branch for the osc-lib update, hope there are no others :P15:34
dhellmanne0ne : why does horizon need a branch of requirements for rc2?15:37
dhellmannthat doesn't sound right15:37
e0nedhellmann: sorry, looks like my mistake. I'll confirm it a bit later today once CI will report on a backport15:37
prometheanfirek, ya, that does sound odd15:37
dhellmannsmcginnis , prometheanfire : we've had some confusion this cycle with the constraints update patches that we create when we open branches. I wonder if we want to wait to create those until we have the requirements branch? it would require separate scripting but we should just have to rearrange some of the pieces we already have15:38
dhellmanne0ne : ok, let us know15:38
smcginnisI was wondering about that too. There does seem to be more confusion than before on that.15:40
smcginnisEven though the commit message says exactly what to expect.15:40
prometheanfiredhellmann: I +2'd one of those updates without realizing we didn't branch first :P15:40
dhellmannsmcginnis : who reads commit messages? ;-)15:40
prometheanfireso maybe ordering is hard15:40
prometheanfiredhellmann: not I15:40
prometheanfirewho needs it15:40
* dhellmann doesns't always15:40
dhellmannI'm not sure what we would use as a trigger15:40
dhellmannmaybe a special case in the branch script15:41
*** annabelleB has quit IRC15:41
dhellmannit would end up having to clone all of the deliverables for the series at once, which might cause problems with job timeouts15:41
dhellmannthe alternative would be to run the script by hand, since that wouldn't have the same timeout problem15:41
openstackgerritMerged openstack/releases master: Tag Rocky release of octavia-tempest-plugin  https://review.openstack.org/59178015:41
dhellmannthat goes against our automation push, though15:42
dhellmannooo, another alternative would be to propose the requirements branch patch and WIP it and then somehow pass that URL to the script that creates all of the constraint update patches so it could be included in a depends-on15:43
dhellmannthat's a bit complicated, though15:43
prometheanfirethat'd have a proper dependency at least15:46
dhellmannyeah15:46
dhellmannthe timeout thing is a real concern, though, so we would want to test that somehow to see how long it would take15:47
smcginnisCould we add a "release" job for the requirements repo that would check if a new branch was created and have that trigger it?15:49
dhellmannhmm15:50
dhellmannthat's a good question15:50
dhellmannI don't know if we can trigger on branch creation15:50
dhellmannfungi, corvus : can we have a job triggered by zuul when a branch is created? ^^15:50
dhellmannit's a ref, so I would think so?15:51
*** annabelleB has joined #openstack-release15:51
corvusdhellmann: yes15:52
corvus(more to come)15:52
dhellmanndo we have any examples we could look at?15:52
*** FracKen has joined #openstack-release15:56
corvusdhellmann: branch creation events should trigger the post pipeline.  you can test for whether it's a created event in the job by checking if https://zuul-ci.org/docs/zuul/user/jobs.html#var-zuul.oldrev is defined.15:56
dhellmanncorvus : ok, so our job would run when something merges and when a branch is created, and we could test for that variable to decide if we need to actually do any work15:58
corvusdhellmann: yep15:59
dhellmannthat should do what we want, thanks!15:59
dhellmannprometheanfire , smcginnis : I made some notes in https://storyboard.openstack.org/#!/story/200344616:03
smcginnisGreat!16:04
dhellmannthere was some other work going on at one point to change the way that constraint list is managed/published so we might want to tie in with that16:04
dhellmanntonyb was doing something but I don't remember the details16:05
prometheanfiredhellmann: I'm thinking of migrating reqs to storyboard now that we only have one bug and just deal with anything else as it comes up16:07
dhellmannsounds good to me16:07
*** pkovar has quit IRC16:09
*** jpich has quit IRC16:25
melwittsmcginnis: re: translations, we were told that the translations are indeed not for rocky and that we are not supposed to backport them. so I think I've not been understanding what the past "rc2 translations" were about16:34
smcginnismelwitt: I think there have been times where repos have gotten translations. It's just been one of the reasons to do an RC2 release.16:35
dhellmannwe used to translate API messages16:41
dhellmannmaybe we're not doing that any more, if they are focused on the documentation and release notes16:42
*** annabelleB has quit IRC16:43
*** annabelleB has joined #openstack-release16:47
*** e0ne has quit IRC16:47
*** ricolin has quit IRC16:50
*** openstackstatus has joined #openstack-release16:58
*** ChanServ sets mode: +v openstackstatus16:58
*** annabelleB has quit IRC17:10
edmondswseveral of the "Update UPPER_CONSTRAINTS_FILE for stable/rocky" commits have already been merged, despite the commit message clearly saying they should not yet17:29
edmondswcould these be proposed later next time, or have a -W until openstack/requirements branches?17:30
*** annabelleB has joined #openstack-release17:32
openstackgerritMatthew Thode proposed openstack/releases master: Branch requirements  https://review.openstack.org/59182317:35
*** dtantsur is now known as dtantsur|afk17:40
smcginnisedmondsw: We were talking about that earlier actually.17:44
smcginnisedmondsw: Seems not many people read commit messages. :)17:44
edmondswseems like it :)17:44
edmondswI can go back and read the history if you've already discussed17:44
smcginnisedmondsw: We might be able to delay having those proposed and have the actual branching of requirements trigger the creation of them.17:44
edmondsw+117:45
smcginnisIt's not an issue in the gate since that passes in a variable, but it can cause problems running tests locally.17:45
*** e0ne has joined #openstack-release17:56
*** ekcs has joined #openstack-release18:05
*** ykarel has joined #openstack-release18:11
tonybdhellmann, smcginnis: Yup IIUC the plan for the constraints publishing will pretty much remove that confusion18:14
smcginnistonyb: What is the plan?18:15
tonybif it had been done then today we'd have valid constraints files releases.o.o/constraints/{rocky,stein}/upper18:16
tonybSo we can always just update it and the state of the requirements repo doesn't matter18:16
smcginnisSo it won't be dependent on branches in the repo?18:16
tonybsmcginnis: It will and it wont.  for and stable branch in requiremenst we'll publish that file "eg constraints/queens/upper" but on master we'll publish both current and current+1 (rocky, stein)18:18
tonybonce we branch we'll switch master to stein and once it's known "train"18:18
smcginnisAh, OK. That sounds like it should ease the transition between release cycles then.18:19
tonybit's a little more work for the requirements team but less on projects and the cross over time is well defined18:19
tonybsmcginnis: It was supposed to happen by now but I didn't do the needed project management so ....18:20
*** electrofelix has quit IRC18:25
dhellmanntonyb , smcginnis : so we'll be doing the constraints switch on master instead of the stable branch?18:35
tonybdhellmann: the realease tooling wont change.18:36
dhellmannthat is, we'd need a patch to change the URL in the tox.ini still, but on master18:36
dhellmann?18:36
dhellmannor is tox going to somehow figure out the URL in a way that doesn't require patches?18:36
tonybdhellmann: It's just that *if* the work had been done we'd have a releases.o.o/constraints/rocky/upper file already18:37
dhellmannyeah, I'm trying to understand how the client side of it will work when we go from stein to tuppence18:37
dhellmanndo we still edit tox.ini each cycle?18:38
tonybdhellmann: Yup we still need the edit18:38
dhellmannok18:38
tonybdhellmann: we're just more flexible on when we do it18:38
dhellmannah, right, I see how that helps now18:38
dhellmannbecause we would have both stein and tuppence published at the same time, that constraints URL patch could land right away18:39
dhellmannin the stable branch18:39
tonybdhellmann: most projects will still do it as a result of the release tooling but it's possible some (like perhaps tripleo) will do it themselves18:39
dhellmannyeah18:39
tonybdhellmann: Yup.  That's how it's supposed to work ;P18:39
dhellmannI think we should probably write all of this out to make sure the details are clear18:39
dhellmannI guess we don't really have specs for the requirements and release work, so maybe an email thread18:40
tonybdhellmann: we had one wheer we came up with the design18:40
dhellmannoh, good18:40
tonybdhellmann: it's just close to a year ago now :/18:40
dhellmannI guess I should go find that18:40
dhellmannbecause I'm left wondering how master ends up getting the right name18:40
dhellmannor is master always just "master"?18:41
tonybdhellmann: It could probably stand a summary ;p18:41
dhellmannI could use a refresher, at least18:41
dhellmannmaybe if we can get that together by the ptg we can find someone to help you with the work18:41
tonybSo today master will publish to both rocky and stein.18:42
tonybonce we branch it drops master18:42
dhellmannwhat's listed in the tox.ini on master?18:42
*** annabelleB has quit IRC18:42
tonybwhen we know what t will we we add that18:42
dhellmannhmm18:42
tonyb... oh and it's also always master18:42
dhellmannah, ok18:42
dhellmannso we still only have to make changes to the URL on the stable branch18:43
dhellmannbut the stable branch name will work even before the repo is branched18:43
dhellmannso on master tox points to a master URL and on the stable branch it points to master and we change it to the branch name18:43
tonybdhellmann: Yup from the release side the process doesn't chnage (but the URL will) it's just that the target URL will exist regardless of the branch existing in requirements18:43
dhellmannwe could roll all of these changes into a single patch on the stable branch if that's the case18:43
dhellmann.gitreview, tox.ini, etc.18:43
dhellmannI wish we could avoid having to patch at all, though18:44
tonybdhellmann: Yup, at some point we resisted doign it in a single patch I don't recall why but times chnage ...18:44
dhellmannwe can't even rely on having those .gitreview patches landed quickly, though, and I don't really see another way to find the branch name accurately18:45
dhellmannwell for now we need .gitreview landed ASAP and we have to wait for the constraints URL update, so that's why they are separate patches today18:45
tonybdhellmann: fro tox.ini can can avoid the patch but it in turn needs a helper in install_cmd18:45
dhellmannif we eliminate the need to wait to land the constraints update we can combine them18:45
dhellmannyeah18:45
tonybdhellmann: Ahh I understand now18:46
dhellmannbut any helper would need to do something to determine the branch, and you can't just look at git for that because locally my branch might be called 'backport-bug-fix' or something and what stable branch is that?18:46
dhellmannso we could read .gitreview to find the branch, but only if the patch to update .gitreview is approved quickly after being proposed18:46
dhellmannwhich in the past they have been, but this cycle I've run into quite a few that weren't18:47
tonybdhellmann: my vauge plan was to use the release data and the version from pbr18:47
dhellmannI actually had to rewrite some of the goal tool scripts to be explicit about the branch where they were proposing patches to deal with that18:47
dhellmannhmm18:47
dhellmannI wonder if we were able to shift things so that we needed to land patches on master instead of the stable branch if that would mean they would be landed faster18:48
dhellmannlike if we put stein in the URL on master, and then when we branch for tuppence we submit the patches on master to use tuppence18:48
dhellmannmore people review patches on master...18:48
*** annabelleB has joined #openstack-release18:49
tonybdhellmann: so I'm typing this straight into IRC so it'll have errors but I was thinking we'd just the same kind of thing we do for docs so that .../constratints/nova/16.*/ redirects to constratints/upper/pike (or whatever the correct mappign is18:49
dhellmannaha!18:49
dhellmannyes, version redirects might help18:49
tonybdhellmann: switching it to that could work18:49
dhellmannas far as the helper, we could release that as a tool, and then tell developers to install tox and that tool18:50
dhellmannthat would avoid the problem we had in the past where the tool was copied around a million places18:50
dhellmannand then diverged18:50
dhellmannbut that also requires special tox config, and we've been moving away from that18:50
dhellmannso maybe let's try publishing with names and changing the names on master before we go down the tool route18:51
tonybYeah, the time I proposed it we settled on the simple branch based static process18:51
tonybYup.  I'll try to get the ball rolling again18:53
dhellmann++19:06
*** openstackgerrit has quit IRC19:19
*** annabelleB has quit IRC19:20
*** annabelleB has joined #openstack-release19:26
*** ykarel has quit IRC19:29
*** onovy has quit IRC19:37
*** onovy has joined #openstack-release19:45
*** annabelleB has quit IRC19:48
*** annabelleB has joined #openstack-release20:01
*** e0ne has quit IRC20:03
prometheanfirereqs is ready to branch btw20:50
smcginnisprometheanfire: OK, I'll hit go on that.20:51
prometheanfiregreen means go20:51
annabelleBdhellmann smcginnis: I was reading through https://review.openstack.org/#/c/591778/ to see the changes, and one of the open patches is for something where (on the patch) they agreed to drop it. Do we apply the “close out your open patches close to the release” rule for cycle-intermediary projects?20:54
smcginnisannabelleB: Usually there are a lot of open patches for most projects. They just miss this release and hopefully get merged early in the next release cycle.20:56
annabelleBsmcginnis: Got it!20:56
smcginnisannabelleB: Which one were you concerned about?20:56
dhellmannif the patch didn't make it we probably want to drop the highlight20:57
smcginnisOh, it's something in the highlights?20:57
annabelleBsmcginnis: https://review.openstack.org/578424 It just caught my eye since it was removing something and I went to check it out20:57
dhellmannannabelleB : if you want to propose a patch to drop the highlight we can get hongbin to +1 it20:57
annabelleBhaven’t seen highlights from them so was hunting through the most recent release changes20:58
*** openstackgerrit has joined #openstack-release20:59
openstackgerritMerged openstack/releases master: Branch requirements  https://review.openstack.org/59182320:59
annabelleBIt’s just a docs change, but made me wonder—just generally—how much we do/don’t enforce closing open things towards the end of cycles21:00
dhellmann"closing open things"?21:01
dhellmannI think we just generally expect teams to keep their code and docs in sync as much as they can21:02
annabelleBseems reasonable21:03
*** masayukig has quit IRC21:12
*** annabelleB has quit IRC22:02
*** ekcs has quit IRC22:08
*** masayukig has joined #openstack-release22:19
*** FracKen has left #openstack-release22:21
*** d0ugal has quit IRC22:33
*** d0ugal has joined #openstack-release22:44
*** d0ugal has quit IRC23:01
*** d0ugal has joined #openstack-release23:03
*** rpioso is now known as rpioso|afk23:12
*** d0ugal has quit IRC23:42
*** d0ugal has joined #openstack-release23:55

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