19:00:00 <tonyb> #startmeeting releaseteam
19:00:01 <openstack> Meeting started Thu Jun  6 19:00:00 2019 UTC and is due to finish in 60 minutes.  The chair is tonyb. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:04 <openstack> The meeting name has been set to 'releaseteam'
19:00:34 <fungi> aloha fine release peoples
19:00:52 <tonyb> hey fungi
19:01:28 <tonyb> smcginnis, diablo_rojo, dhellmann, evrardjp: Are you around for the releaseteam meeting?
19:01:39 <smcginnis> o/
19:01:48 <armstrong> o/
19:01:59 <smcginnis> Kudos on the prompt start again. :D
19:02:43 <diablo_rojo> o/
19:02:57 <tonyb> smcginnis: thanks
19:03:31 <fungi> my #startmeeting irc highlight is apparently working great ;)
19:03:37 <tonyb> smcginnis: gotta have goals
19:04:13 <tonyb> fungi: :) I might have to borrow that trick
19:04:33 <fungi> it's belt-n-braces with my reminder utility
19:04:41 <tonyb> hey armstrong nice to you again
19:05:05 <armstrong> thanks
19:05:23 * tonyb winders if diablo_rojo is ever not jetlagged?
19:05:43 <fungi> she doesn't actually sleep
19:05:59 <tonyb> fungi: ahhh that'd do it
19:06:18 <tonyb> #link https://etherpad.openstack.org/p/train-relmgt-tracking
19:06:28 <tonyb> somehwere near line 157
19:06:53 <tonyb> ttx: has done another great job on the agenda
19:07:37 <diablo_rojo> Sleep is for the weak
19:07:49 <tonyb> #topic tasks
19:08:05 <tonyb> The only task is: Check tripleo repos have correct deliverable type.
19:08:35 <smcginnis> I believe we've sorted that out and they should be correct for train.
19:08:45 <tonyb> smcginnis: Ahh cool
19:09:06 <tonyb> smcginquick topic then ;P
19:09:31 <tonyb> #topic Completion of train-1 changes
19:10:07 <tonyb> diablo_rojo: anything to say on the Track release liaisons in deliverable files item?
19:10:32 <tonyb> (noting we actually now mean release_liaisons.yaml
19:11:51 <diablo_rojo> Is the current format good with everyone?
19:12:03 <diablo_rojo> I feel like I've formatted things differently each patchset lol
19:12:57 <tonyb> Well seesin as you said that ....
19:13:21 <tonyb> can we have the project as the keyname the the main dict?
19:13:58 <tonyb> so: zun:\n- name:...\nirc: ...\n etc?
19:14:19 <smcginnis> I think we need that to be able to have a list of liaisons per project.
19:14:34 <smcginnis> Or else need to match them up in code, but that seems inefficient.
19:14:51 <smcginnis> diablo_rojo: Have you worked on any code to actually consume this to get a better feel for its usage/
19:14:57 <tonyb> smcginnis: Well we can have a key in each person
19:15:24 <smcginnis> tonyb: Yeah, that's what I meant about then having to match them up in code.
19:15:30 <smcginnis> Easier to just have the project with the list of liaisons.
19:15:58 <tonyb> smcginnis: +1
19:16:03 <smcginnis> Should be really easy to script the creation of this file too. That might be a useful exercise, even if the script might be throw away.
19:16:22 <diablo_rojo> I think I had the project as the top level construct in the last patchset..
19:16:30 <smcginnis> Although... we probably would want to keep that script if we every need to do periodic updates until we drop the wiki table.
19:16:36 <diablo_rojo> But I can change it back
19:17:03 <smcginnis> Patchset 2 did, but had other issues.
19:17:43 <diablo_rojo> Okay. I'll go back to that then (sans the other issues)
19:18:29 <smcginnis> If you script the creation, then you won't need to worry as much about the yaml syntax.
19:18:43 <tonyb> diablo_rojo: Thanks.  I think we're close now
19:18:47 <tonyb> smcginnis: true
19:20:03 <diablo_rojo> I'll look into it.
19:20:43 <tonyb> #topic Look up progress on must-do improvements
19:20:46 <fungi> if you want any suggestions for yaml emitters, i've worked out how to coerce pyyaml into dumping in a format that yamllint will tolerate
19:21:21 <smcginnis> We should have a few examples in the repo already with things like new-release.
19:21:37 <fungi> (takes a bit of overriding its built-in list indentation methods)
19:21:40 <tonyb> fungi: thanks, we have yamlutils in repo that can do what we need ;P
19:22:01 <fungi> oh, cool. it generates lintable yaml?
19:22:26 <tonyb> fungi: I think so?
19:22:29 <fungi> though perhaps it's just as easy to tell yamllint to ignore generated files
19:23:03 * tonyb will have to look at that later #curiousnow
19:23:27 <tonyb> the cwi changes I did yesterday used the 2 tools I'm supposed to create
19:23:44 <tonyb> so I'll clean them up a little today and push them
19:24:10 <smcginnis> Nice!
19:24:14 <tonyb> It's a lot more fiddly than I expected
19:24:44 <tonyb> I looked at interactive-release and it has a few issues that I thought made it harder to use than I'd like
19:25:05 <tonyb> so I just borrowed the core of it and add --interactive to new-release
19:25:16 <tonyb> which worked quite well
19:25:22 <tonyb> for a first pass
19:26:16 <tonyb> for ttx's task Add a tool script for producing the list of intermediary deliverables that have not released https://storyboard.openstack.org/#!/story/2005707
19:26:26 <tonyb> he say's no progress
19:27:07 <tonyb> which is ok
19:28:01 <tonyb> #topic Assign/drop should-do improvements
19:29:22 <tonyb> Anyone feel strongly about Engage with QA on communicating classification rates regularly
19:29:35 <tonyb> smcginnis: I think that was your idea after the last cycle?
19:29:55 <smcginnis> I can't recall that. :)
19:30:08 <fungi> as in recurrent test failure classification ni elastic-recheck?
19:30:19 <tonyb> IIRC it was trying to keep an eye on the 'unclassified' rate in e-r hoping to not have a bunch of gate/ci bugs late in the cycle
19:30:20 <smcginnis> Maybe just the wording. I'm not sure what "classification rates" means.
19:30:41 <smcginnis> Ah, not sure that was from me, but I think I recall that coming up.
19:31:19 <tonyb> smcginnis: okay sorry I thought it was you
19:31:32 <tonyb> anyone want to reach out the QA team?
19:31:42 <smcginnis> I'm not really sure how we could go about that, at least easily. But if someone wants to write some sort of script to get some stats there that we could use as an indicator of potential problems, that might be good.
19:33:36 <tonyb> Yeah I feel like doing it well is a pretty big job
19:34:06 <smcginnis> Might be something that while useful, we may not have the bandwidth to really tackle at this time.
19:34:10 <tonyb> we shoudl be able to get the stats out of e-r but then someone needs to try and classify the unclassified failures :/
19:34:42 <tonyb> Yeah we were hoping to make it sound really usful to QA so they can run with it ;P
19:34:50 <smcginnis> ;)
19:35:06 <tonyb> but it isn't like any team has surplus members these days :(
19:35:18 <tonyb> ok
19:35:34 <tonyb> Audit OUI traning material to make sure it matches the current process/tools https://storyboard.openstack.org/#!/story/2005709
19:35:36 <openstackgerrit> Merged openstack/releases master: [nova] Create milestone-1 releases  https://review.opendev.org/663642
19:35:37 <openstackgerrit> Merged openstack/releases master: Releases for Octavia and python-octaviaclient  https://review.opendev.org/663452
19:35:51 <tonyb> anyone?
19:36:09 <tonyb> It was my idea so I s'pose I'm default
19:37:29 <smcginnis> Last I think I saw it was in Berlin. I think there was just a slide or two on our release process?
19:38:09 <tonyb> smcginnis: There's docs in the contributor guide which we need to check and then 3-4 questions about the release process
19:38:20 <smcginnis> K
19:38:47 <tonyb> smcginnis: I wanted to make sure that the docs were right and the questions focused on the parts of the process that are a) current and b) interesting/important
19:39:02 <smcginnis> Seems like a good thing to review then.
19:39:22 <smcginnis> tonyb: Thanks for volunteering to do that. :P
19:39:48 <tonyb> okay I'll take it but it will probably happen like days before Shanghai
19:40:11 <smcginnis> Nothing like a deadline to actually motivate. ;)
19:40:18 <tonyb> smcginnis:  ;P
19:40:22 <tonyb> Update branch creation script to add new python job template on master as part of opening a new series (see https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html#unit-tests for details;
19:40:55 <smcginnis> I think this was assuming we would have openstack-python-train-jobs templates defined?
19:41:07 <smcginnis> s/train/$SERIES/g
19:41:34 <tonyb> I think making sure we have openstack-python-train-jobs as part of opening master for train so yeah as you say makign sure it is
19:41:51 <tonyb> when we do the same for U8
19:41:57 <tonyb> U*
19:42:23 <smcginnis> That could save a lot of work. We would need to make sure that template is defined in time, then have a way to tell which $SERIES to drop in there.
19:42:39 <tonyb> I think we can assume that the template exists (or we can make sure it does as part of our process)
19:42:49 <smcginnis> ++
19:43:26 <tonyb> then IIUC what dhellmann is suggetsing is when we open master for $project we switch to the right job ... similar to the constraints or reno stuff
19:43:31 <smcginnis> So we would have updating that job template, updating the upper-constraints URLs in tox.ini, and adding the stable reno landing page.
19:43:41 <smcginnis> +1
19:44:13 <tonyb> I wonder how much variation per project we'll get
19:44:15 <tonyb> ?
19:44:17 <smcginnis> Would make that boilerplate stuff a lot easier. Assuming there isn't a new python version in the template that breaks.
19:44:29 <smcginnis> I would hope there isn't much variation.
19:44:42 <tonyb> [tony@thor nova]$ git grep openstack-python-train-jobs
19:44:42 <tonyb> [tony@thor nova]$
19:44:43 <smcginnis> Other than how quickly they would respond and actually merge it.
19:44:53 <fungi> speaking of should-do things, i bet we're past due to for our artifact signing key transition. i'll put that on my to do list for the next week
19:44:55 <tonyb> D'oh
19:45:12 <tonyb> No wait that's right we shoudl have train jobs now
19:45:19 <smcginnis> fungi: I thought we did that at the end of stein? Or are you saying we never actually switched over to the new one?
19:45:28 <fungi> the key has existed and been attested to a fair amount, just need to swap it into production
19:45:46 <tonyb> fungi: Thanks
19:45:50 <fungi> we have that as separate steps, one before release and the other shortly after
19:45:50 <smcginnis> tonyb: I've seen patches out there, but since it wasn't automatic, it's been very hit or miss from folks going around and proposing it.
19:46:00 <fungi> thought we had it on the release timeline but i may have imagined that
19:46:06 <smcginnis> fungi: Ah, yep, I think it's time.
19:46:26 <tonyb> fungi: Should we add that to the process for between release and m1?
19:46:29 <smcginnis> We should maybe add a reminder in our process doc between start and m-1.
19:46:58 <fungi> yeah, that sounds like the right timeframe
19:47:11 <tonyb> smcginnis: I think I'll do some research on that to see how much work it'll be
19:47:27 <fungi> we used to defer until after the cycle-trailing release deadline, but not that there's no deadline for those we agreed it could happen any time after the coordinated release date
19:47:44 <smcginnis> That makes sense.
19:47:45 <fungi> er, now that there's no deadline
19:47:46 <tonyb> I like the idea of automating it but getting things up to a level where we can may be a bigger effort
19:48:07 <tonyb> fungi: okay
19:48:24 <smcginnis> tonyb: I suppose if we at least scope out the work effort, then we can figure out if we can make it happen by U.
19:48:34 <fungi> switching it into production is as easy as making a couple changes (one to the job config, one to the release docs)
19:48:42 <smcginnis> Speaking of... any progress on choosing a U name?
19:49:19 <tonyb> smcginnis: Not enough
19:49:51 <smcginnis> :/
19:49:53 <fungi> i'm lobbying for an exception to call it "unpossible" (because apparently it nearly is)
19:49:58 <tonyb> smcginnis: ekcs is helping abd he's don his bit, diablo_rojo even built me a wiki page I just need to pull the 2 bits togther and then ask the TC if I can run it
19:50:03 <smcginnis> That works for me!
19:50:19 <tonyb> fungi: You can suggest that once I have the wiki
19:50:27 <fungi> sounds like it's been a herculean effort this time
19:50:46 <fungi> thanks for coordinating that
19:50:58 <tonyb> fungi: not really, just more effort than T because of the location
19:51:36 <fungi> harder than i because we don't have leftover names from a british colony to fall back on this go round
19:51:39 <tonyb> fungi: there are quite a few candidates, I don't know how good they are but ekcs found 10+ in his checking
19:51:56 <smcginnis> Wow, that's better than I was expecting.
19:52:11 <tonyb> ... assuming we allow non pinyin romanisation
19:52:26 <smcginnis> We probably need to.
19:52:33 <fungi> i expect we have no alternative
19:53:02 <tonyb> Well this will sound terrible I don't know how easy they'll be to say/use but that's what the poll is for
19:53:38 <fungi> we'll end up naming it "ulong" because of all the oolong tea we'll be drinking there
19:53:47 <smcginnis> ++
19:53:55 <tonyb> :)
19:54:02 <smcginnis> Added bonus that it is an unsigned long.
19:54:16 <fungi> yeah, geek humor ftw
19:54:21 <tonyb> but then everytime I see it I'll think of unsigned long int :(
19:54:50 <fungi> what, you'd prefer something with less precision?
19:55:12 <smcginnis> ushort just isn't big enough.
19:55:12 <fungi> i'll be happy to float some ideas
19:55:18 <diablo_rojo> Bunch of nerds ;)
19:55:21 <tonyb> ;P
19:55:27 <smcginnis> fungi: That was bad. Love it.
19:55:52 <fungi> my jokes are going over better today in here than in #zuul
19:56:00 <fungi> i almost got hit with virtual rotten vegetables
19:56:02 <tonyb> fungi: more worlds colliding
19:56:30 <tonyb> you heard it here folks we're nicer than #zuul :D
19:56:40 <smcginnis> :D
19:57:15 <tonyb> Anything else for the last 3mins?
19:57:49 <smcginnis> Nah
19:58:06 <tonyb> okay
19:58:23 <fungi> planning to remove the bindep fallback package list and the zuul-cloner shim from non-legacy jobs in the opendev zuul
19:58:24 <tonyb> going twice?
19:58:40 <tonyb> fungi: eeek
19:58:44 <fungi> shouldn't wreak havoc for release jobs, but tentatively june 24-ish
19:59:11 <tonyb> fungi: cool, if you have a list of things we should check that'd be good
19:59:17 <smcginnis> Does that mean repos that don't have bindep files may hit issues now?
19:59:19 <fungi> we're doing a bit more exploratory testing before we set a firm date
19:59:52 <smcginnis> I think tonyb is watching that clock.
19:59:55 <fungi> repos that don't have bindep files but are running jobs which don't install stuff they require which were included in the fallback list may run into issues, yes
20:00:00 <tonyb> #endmeeting