Thursday, 2019-05-16

*** armax has quit IRC00:45
*** diablo_rojo has quit IRC00:45
*** ricolin has joined #openstack-release00:50
*** d34dh0r53 has joined #openstack-release01:01
*** armax has joined #openstack-release01:02
*** ekcs has quit IRC01:04
*** armax has quit IRC01:37
*** lbragstad has quit IRC01:42
*** lbragstad has joined #openstack-release01:51
*** whoami-rajat has joined #openstack-release02:06
*** dhellmann has quit IRC02:23
*** dhellmann has joined #openstack-release02:23
*** binh_ has quit IRC02:32
*** binh_ has joined #openstack-release02:33
*** nhbinh_ has joined #openstack-release02:36
*** binh_ has quit IRC02:38
*** binh_ has joined #openstack-release02:38
*** binh___ has quit IRC02:38
*** lbragstad has quit IRC02:40
*** lbragstad has joined #openstack-release02:43
*** armax has joined #openstack-release02:45
*** armax has quit IRC03:05
*** hongbin has joined #openstack-release03:14
*** ykarel|away has joined #openstack-release03:40
*** ykarel|away is now known as ykarel03:49
*** radeks_ has joined #openstack-release03:50
*** udesale has joined #openstack-release03:53
*** hongbin has quit IRC03:55
*** radeks_ has quit IRC04:40
*** lbragstad has quit IRC04:59
*** ykarel is now known as ykarel|afk05:12
*** _d34dh0r53_ has joined #openstack-release05:12
*** ykarel|afk has quit IRC05:16
*** ykarel|afk has joined #openstack-release05:31
*** ykarel|afk is now known as ykarel05:31
openstackgerritAndrey Kurilin proposed openstack/releases master: [Rally] Release a nwe version with a fix to previous release
*** e0ne has joined #openstack-release05:53
*** radeks_ has joined #openstack-release06:03
*** radeks_ has quit IRC06:04
*** radeks_ has joined #openstack-release06:04
*** udesale has quit IRC06:05
*** udesale has joined #openstack-release06:06
openstackgerritMerged openstack/releases master: Release cinderclient 4.2.0
openstackgerritMerged openstack/releases master: Oslo stein releases for 2019-05-06
openstackgerritTony Breeds proposed openstack/releases master: Add Cinder Specific Events for Train
openstackgerritMerged openstack/releases master: Oslo rocky releases for 2019-05-06
openstackgerritMerged openstack/releases master: Release monasca-agent 2.6.3
openstackgerritMerged openstack/releases master: Rename to
openstackgerritMerged openstack/releases master: Final pike release
openstackgerritMerged openstack/releases master: Initial python-mistralclient Train Release
openstackgerritMerged openstack/releases master: Add Train cycle schedule for manila
*** e0ne has quit IRC06:36
openstackgerritMerged openstack/releases master: Release 0.28.0 of openstacksdk
openstackgerritMerged openstack/releases master: oslo.serialization 2.29.1
openstackgerritMerged openstack/releases master: train: release python-novaclient 14.0.0
openstackgerritMerged openstack/releases master: [Rally] Release a nwe version with a fix to previous release
*** udesale has quit IRC06:51
*** udesale has joined #openstack-release06:52
*** udesale has quit IRC07:02
*** openstackgerrit has quit IRC07:03
*** udesale has joined #openstack-release07:03
*** jaosorior has quit IRC07:06
*** pcaruana has joined #openstack-release07:13
*** udesale has quit IRC07:36
*** udesale has joined #openstack-release07:37
*** amoralej|off is now known as amoralej07:41
ykarelsmcginnis, hi, rememeber the discussion regarding mistralclient, u said u-c for master will not be updated07:43
ykareli see it's updated
*** hberaud has joined #openstack-release07:45
ykarelseems some issue, can you check once available07:46
*** ykarel is now known as ykarel|lunch07:46
*** tosky has joined #openstack-release07:48
tonybykarel|lunch: can you elaborate?  all realeases publish to pypi typically get "bumped" in u-c08:00
tonybykarel|lunch: Oh I see, it's a stein release so you thought it shouldn't land on master08:04
tonybykarel|lunch: If that's the case you'll need to revert it on master but here should be a good reason as it'll keep getting added back on master08:05
tonybykarel|lunch: So there are 2 processes in play here08:07
*** e0ne has joined #openstack-release08:08
tonybykarel|lunch: when we cut a release on $branch a review on the same branch will be generated to match ( in this case08:09
tonybI'm pretty sure that's what smcginnis was referring to08:09
tonybbut then we have a second tool that runs daily and looks for new releases on master and then proposes them as an update08:10
tonybwhich is then review that you're referencing08:10
tonybykarel|lunch: I see which was made by the 3.9.0 release from master which I think fixes things for you08:11
tonybykarel|lunch: the "race" here shoudl only happen early in a cycle08:12
*** openstackgerrit has joined #openstack-release08:15
openstackgerritTony Breeds proposed openstack/releases master: Add Cinder Specific Events for Train
*** cdent has joined #openstack-release08:25
*** ykarel|lunch is now known as ykarel08:33
ykareltonyb, yes i meant:  it's a stein release so you thought it shouldn't land on master08:36
ykareland I see which was made by the 3.9.0 should fix master u-c08:36
ykarelas 3.9.0 released against train08:36
ykareltonyb, re. but then we have a second tool that runs daily and looks for new releases on master and then proposes them as an update, where it checks releases?08:37
ykarel3.8.1 was tagged only for stable/stein08:37
tonybykarel: right but it's published to pypi and the constraints tool just knows that 3.8.1 > 3.8.0 to it installed 3.8.1 and proposed that change08:38
tonybthat tool knows nothing about OpenStack release process or branches (and shouldn't have to)08:39
ykareltonyb, ohhk got it, the issue should go after first train release08:39
tonybykarel: correct08:39
ykareltonyb, Thanks for all the explanations08:39
tonybykarel: and if 3.9.0 had happend first, wouldn't have happened at all08:39
ykarelyup got it08:39
tonybykarel: So once 659458 merges we shoudl be good08:41
*** dtantsur|afk is now known as dtantsur08:50
*** hberaud is now known as hberaud|lunch10:03
*** ykarel is now known as ykarel|meeting10:07
*** tosky has quit IRC10:10
*** tosky has joined #openstack-release10:11
*** jaosorior has joined #openstack-release10:12
*** pcaruana has quit IRC10:27
*** ricolin has quit IRC10:39
*** hberaud|lunch is now known as hberaud10:52
*** ykarel|meeting is now known as ykarel10:53
*** amoralej is now known as amoralej|lunch11:04
*** ykarel is now known as ykarel|afk11:11
*** udesale has quit IRC11:15
*** pcaruana has joined #openstack-release11:37
*** dtantsur is now known as dtantsur|brb11:46
*** ykarel|afk is now known as ykarel11:59
*** amoralej|lunch is now known as amoralej12:32
*** udesale has joined #openstack-release13:02
*** lbragstad has joined #openstack-release13:09
*** mriedem has joined #openstack-release13:15
*** dtantsur|brb is now known as dtantsur13:18
smcginnisykarel: Sorry for the confusion. Tony had a much better explanation of it all. I wasn't thinking about the automatic update job that runs separately.13:24
*** ianychoi has joined #openstack-release13:26
openstackgerritMerged openstack/releases master: Add Cinder Specific Events for Train
ykarelsmcginnis, yeah it can be missed some times as there are too many things going on :)13:45
*** pcaruana has quit IRC13:56
*** ykarel is now known as ykarel|afk14:14
*** ykarel|afk is now known as ykarel14:15
*** ykarel is now known as ykarel|away14:17
*** mlavalle has joined #openstack-release14:22
*** d34dh0r53 has quit IRC14:36
*** d34dh0r53 has joined #openstack-release14:37
*** armax has joined #openstack-release14:37
*** pcaruana has joined #openstack-release14:37
*** d34dh0r53 is now known as Guest2890414:41
*** samP has quit IRC15:28
*** samP has joined #openstack-release15:29
openstackgerritAlex Schultz proposed openstack/releases master: [tripleo] create pike-em tag against final releases
*** _d34dh0r53_ is now known as d34dh0r5315:38
*** e0ne has quit IRC15:38
*** ricolin has joined #openstack-release15:38
*** ykarel|away has quit IRC15:44
*** pcaruana has quit IRC15:47
*** ykarel|away has joined #openstack-release16:04
*** dims has quit IRC16:05
*** cdent has quit IRC16:17
*** dtantsur is now known as dtantsur|afk16:19
*** ykarel|away has quit IRC16:22
clarkbsmcginnis: we've restarted zuul with the fix for the js release job in place16:31
smcginnisclarkb: Thanks!16:31
*** ricolin has quit IRC16:44
clarkbsmcginnis: as another heads up we want to restart gerrit to fix the gitweb links16:52
clarkbso you should hold off on release activities for a bit longer16:52
clarkbwe are waiting for to do its thing16:53
*** bauzas has quit IRC16:54
openstackgerritMerged openstack/releases master: [tripleo] create pike-em tag against final releases
*** bauzas has joined #openstack-release16:57
*** dims has joined #openstack-release17:03
*** lbragstad has quit IRC17:05
*** amoralej is now known as amoralej|off17:12
*** dims has quit IRC17:12
*** lbragstad has joined #openstack-release17:13
*** dims has joined #openstack-release17:13
*** ykarel|away has joined #openstack-release17:17
-openstackstatus- NOTICE: Gerrit is being restarted to add gitweb links back to Gerrit. Sorry for the noise.17:37
*** electrofelix has quit IRC17:38
*** pcaruana has joined #openstack-release17:39
*** hberaud is now known as hberaud|gone17:46
*** udesale has quit IRC17:46
*** ianychoi has quit IRC18:15
*** ykarel|away has quit IRC18:28
*** armstrong has joined #openstack-release18:32
*** trident has quit IRC18:51
*** trident has joined #openstack-release18:52
* tonyb waves18:53
* smcginnis waves back18:56
tonybhey armstrong!18:57
tonybarmstrong: good to see you18:57
armstrongI missed last week meeting :) time zone thing18:58
tonybarmstrong: It's okay.  TZs are hard ;P18:58
tonyb#startmeeting releaseteam19:00
openstackMeeting started Thu May 16 19:00:00 2019 UTC and is due to finish in 60 minutes.  The chair is tonyb. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: releaseteam)"19:00
openstackThe meeting name has been set to 'releaseteam'19:00
tonybttx dhellmann diablo_rojo hberaud evrardjp fungi armstrong: Release team meeting is starting19:00
openstackgerritSean McGinnis proposed openstack/releases master: [monasca] final releases for pike
* tonyb will point out that the start time was "Thu May 16 19:00:00 2019 UTC" #nailedit!19:00
smcginnisTests took 30 seconds too long.19:00
smcginnisHaha, nice!19:00
tonybsmcginnis: gotta take the wins ;P19:01
evrardjpo/ (but commuting back home so that I can have my laptop)19:01
tonybttx: has (as always) set us up with a good agenda19:02
tonybokay let's start19:03
tonyb#topic Confirm task assignments from
*** openstack changes topic to "Confirm task assignments from (Meeting topic: releaseteam)"19:03
ttxSo there were a fez open question marks on last week assignment exercise19:04
tonybYup we have evrardjp here today so ...19:04
* smcginnis wants an official release team fez19:04
ttxOn the process changes we had to complete by train-1...19:04
diablo_rojo_phonSo we can assign him a bunch of stuff.19:04
ttxDo stable autoreleases around milestones: evrardjp?19:04
ttxTrack release liaisons in deliverable files: diablo_rojo?19:05
* diablo_rojo_phon agrees with smcginnis's fez idea19:05
diablo_rojo_phonYeah I can take that one.19:05
tonybI was thinking he can let us know his capacaity but sure we can just give it all to him ;P19:05
ttxevrardjp: are you ok with driving that change?19:06
evrardjpI am not yet sure if I can take this, tbh.19:06
ttxdo we have anyone else who could take it? needs to be completed soon enough19:06
evrardjpthat's the problem for me19:06
ttxI can't, my travel schedule in crazy in june19:06
tonybI can do the scripting side of things but the hard part is looking at each deliverable and making the call on if it needs to be released19:07
smcginnisI'm hesitant to sign up for anything because I'm not sure how much time I am going to have to devote to things soon, but I'm willing to help someone else.19:07
tonybttx: I did notcie that ;P19:07
ttxt-1 is in 3 weeks19:07
ttxI mean it's also crazy in May19:07
*** ekcs has joined #openstack-release19:08
smcginnistonyb: I had looked at making the scripting interactive where it could print out the changes, then you y/n whether anything requires a release.19:08
ttxcome to think of it, July is not really better :|19:08
diablo_rojo_phon....I could maybe take it. With help.19:08
diablo_rojo_phonMy June doesn't suck.19:08
diablo_rojo_phonJust the rest of this month.19:08
evrardjplucky you19:08
tonybI think you're traveling too much :/19:08
ttxhmm, do we NEED to have it done by train-1?19:08
tonybttx: I was just going to ask that19:09
ttxI said t1 because we kinda wanted to do that milestone in autorelease19:09
funginot really on-topic, but tonyb mentioned a great meeting agenda just didn't link to it (and the irc-meetings data doesn't include one either)... can haz link?19:09
tonybit was a preety soft "lets do it at this time" rather than a hard "it must be done"19:09
ttxbut I guess we could also not do anything for t119:09
evrardjpWe can work on it this cycle and put that 'in prod' for next ? ;)19:09
tonybfungi: sorry19:10
smcginniss/train-1/as soon as possible/19:10
ttxevrardjp: we ship to prod here19:10
tonybLine 134'ish19:10
ttxevrardjp: could you take it if it was a t2 thing?19:10
ttx(July 24)19:10
evrardjpprobably the same as t119:11
evrardjpso I would say no.19:11
evrardjpbut after it looks better19:11
evrardjp"theoretically "19:11
ttxsmcginnis: could you mentor diablo_rojo through it ?19:12
evrardjpsorry :/19:12
tonybevrardjp: It's all good.19:12
tonybevrardjp: You can make it up to us later ;P19:13
smcginnisttx: Sure, I can help.19:13
tonybsmcginnis: thanks19:13
ttxOK so I'll move that task on the PTG doc to t2 and make it diablo_rojo mentored by smcginnis19:14
evrardjpthx ttx19:14
diablo_rojo_phonIf we did it for T1 what's the actual date on that?19:14
tonybthat'll mean we can use the liasion stuff diablo_rojo_phon is doing/will do19:14
ttxbefore June 619:14
ttxI mean you can always finish before19:15
diablo_rojo_phonsmcginnis if you're free the fee days leading up to that I think we can have it done then.19:15
smcginnisWe can also start with a crawl, walk, run approach and start semi-manual/semi-automated and work towards complete(r) automation later.19:16
* tonyb likes smcginnis idea to add '--interactive' to new-release which will help with this19:16
ttxWe also had a must-do improvement19:16
ttxAdd a tool script for producing the list of intermediary deliverables that have not released19:16
ttxI'll do that one if nobody else wants it19:16
evrardjptonyb : agreed19:16
smcginnisThat one is basically a wrapper around the existing commands to make the task easier, right?19:17
tonybttx: I think it's yours ;P19:17
ttxsmcginnis: I guess19:17
smcginnisGoing once, going twice, sold to ttx19:17
ttxhaven't looked :)19:17
evrardjpsmcginnis: I like your style19:17
ttxok, I have nothing more on this topic19:18
dhellmanntonyb , smcginnis : regarding the interactive mode, harlowja built a tool like that in the repo already (don't remember the name, but look at the list of cli apps in setup.cfg)19:18
dhellmannI think it's out of date, but it should be possible to update it19:18
dhellmannor at least crib from it to update new-release19:18
tonybdhellmann: Yup I do recall that19:18
smcginnisThat would be great to have a starting point.19:18
tonybinteractive-release ?19:19
smcginnisHuh, would you look at that. :)19:19
smcginnisMight be worth doing an inventory of all our commands and tools and get that all in once place with short descriptions.19:19
dhellmannI thought we had that in the readme, too, but maybe not19:20
tonybIt's in the readme19:20
dhellmannthat's probably out of date, too19:20
smcginnisI think we do for the tools we want others to use. Maybe not.19:20
dhellmannman, the old release team was really a bunch of slackers19:20
smcginnisYeah, likely could use a refresh at any rate.19:20
evrardjpdhellmann: haha19:20
ttxespecially the last 3 PTLs19:20
tonybOkay I'll do that19:20
tonybat least those PTLs could send email on time .. this new PTL ... what a schmuck!19:21
ttxnow onto pike-em fun19:21
dhellmannemail on time or meeting on time, pick one19:21
smcginnistonyb: To be fair, I think it took me a few weeks to get into the habit.19:22
tonybsmcginnis: I'll take it19:22
tonyb#topic pike-em19:22
*** openstack changes topic to "pike-em (Meeting topic: releaseteam)"19:22
smcginnisMonasca should be ready to go now. Then we just need to update the pike-em tagging patch.19:23
* ttx fetches a drink19:23
diablo_rojo_phonI emailed the four PTLs/liaisons.19:23
smcginnisYeah, a few of them have shown more attention the last few days, so that has helped.19:23
tonybLooks like tripleo is released we just need the pike-em tag19:24
smcginnisTricircle is stuck pending an update for the sphinx requirements that's blocking the README fixes needed.19:24
diablo_rojo_phonGlad it want wasted effort :)19:24
smcginnisI think I just pushed tripleo a little earlier.19:24
evrardjpyup saw that :) thanks smcginnis19:24
smcginnisWe have monasca (ready), tricircle, and puppet.19:25
tonybso how much longer do we give tricircle or puppet?19:25
tonyband heat is a whole other question19:25
smcginnisA couple heat and ansible issues that are bigger.19:26
tonybwe did say today we'd just tag the existing releases as pike-em and declare it done19:26
evrardjpansible ?19:26
smcginnisdiablo_rojo_phon: Is that what you communicated? ^^19:26
diablo_rojo_phonI said if there was no action by today we'd just tag them19:26
evrardjpsomething new I should be aware ?19:26
tonybevrardjp: Line 11819:27
smcginnisevrardjp: Links to failures in the etherpad, but os_molteniron had a releasenotes job failure and python-pankoclient had a tagging failure.19:27
smcginnisThe python-pankoclient failure is a bit odd.19:27
tonybUmm yeah that is odd19:28
evrardjpI see, it's probably with the fact we discussed retiring this repo19:28
evrardjpbut it isn't retired yet19:28
smcginnisSo maybe both of those are safe to ignore and we can just do the final taggin?19:29
smcginnisErr, wait. I think these were on the final taggin.19:29
evrardjpI can't judge for pankoclient19:29
smcginnisGah, can't spell ing.19:29
tonybsmcginnis: yeah I think at least pankoclient was the pike-em tag19:29
tonybsmcginnis: and the tag is in that repo19:30
fungiwere there any failures associated with the zuul artifacts issue yesterday which need to be rerun? we had to dequeue some refs, i think tripleo-ui at a minimum19:30
smcginnisfungi: None I've seen.19:30
smcginnisos_molteniron has the pike-em tag too.19:30
smcginnisSo I guess we're good.19:30
tonybfungi: like what smcginnis said ;P19:30
smcginnisSo Heat's the big question mark at this point.19:31
smcginnisBut also maybe something we can just ignore and move on.19:31
tonybwe can fix it but that kinda means a new release19:31
tonybI kinda think just declare pike-em done ... with some issues and aim for better with queens19:32
smcginnisI'm fine with that.19:32
tonybwhich *should* be better if we do the automatic releases we disussed19:32
smcginnisWe'll hit this with queens too, so either we need to get them to do some work, or we can just expect it and ignore it again.19:32
dhellmannwhat's the story with heat? is there something blocking the name change?19:32
tonybless bitrot anyway, and less delta from the last release19:32
smcginnisdhellmann: They changed from heat to openstack-heat in later (sooner?) branches, but didn't go back to pike and queens with those updates.19:33
dhellmannyeah, so they just need to fix that, right?19:33
tonybdhellmann: I don't think it's blocked just hasn't been done19:33
tonybdhellmann: Yup19:33
smcginnisThat would make things a little easier.19:33
dhellmannas long as it's just a matter of not doing it19:33
dhellmanntell them there won't be any new releases from any branch until that's done :-)19:33
tonybdhellmann: ;P19:34
diablo_rojo_phonHaha :)19:34
dhellmannor, you know, make the validation job report that failure19:35
dhellmanndo what you have to19:36
evrardjpthat doesn't sounds like a problem a little socialization wouldn't fix19:37
tonybdhellmann: validation is already failing19:37
dhellmanntonyb : yeah, I was making a joke about having it fail on master, too19:38
dhellmann"all branches must be publishable"19:38
tonybevrardjp: I think the only tension really is our desire to get the pike-em stuff off the plate and the (probably small) delays that fixinx it in heat will take19:38
evrardjpmakes sense19:38
tonybthe heat team is alsmost certainly okay with it and has been pretty responsive19:38
tonybdhellmann: ahh sorry I missed it ;P19:39
tonybLet's just fix queens and declare pike done, as per the email diablo_rojo_phon sent19:40
tonybit's a little unfair to heat but then we can put pike behind us19:41
diablo_rojo_phonWorks for me.19:41
tonybokay moving on19:42
smcginnisSo just to make sure I have the plan, drop any outstanding final releases (other than Monasca that is ready to go) and update the pike-em patches to just use the last successfully release versions.19:42
tonyb#topic Do we want to add per-projects links for Feature freeze19:42
*** openstack changes topic to "Do we want to add per-projects links for Feature freeze (Meeting topic: releaseteam)"19:42
tonybsmcginnis: correct19:42
tonybso on $topic19:42
smcginnisI raised this one on a few reviews of project specific deadlines.19:42
smcginnisA few have added $project Feature Freeze on the overall feature freeze week.19:42
smcginnisSo.. a bit redundant IMO as that applies to everyone already.19:43
ttxI'd say unless they have a specific thing it's not worth mentioning each19:43
diablo_rojo_phonI think if it's different than the official feature freeze (like being earlier)  it would be fine.19:43
diablo_rojo_phonBut it doesn't make sense to restate what is already there.19:44
smcginnisYeah, earlier is good and should definitely be called out.19:44
smcginnisSo everyone OK if I put up a patch to remove those?19:44
diablo_rojo_phonFine by me.19:44
smcginnisWe could even still leave the text descriptions in under the project section, just not have them linked from the weekly table.19:44
tonybsmcginnis: yup19:45
smcginnisOK, I'll take that action then if no one is against the idea.19:45
tonybsmcginnis: all yours19:45
tonyb#topic openstack-manuals owned by releases team?19:46
*** openstack changes topic to "openstack-manuals owned by releases team? (Meeting topic: releaseteam)"19:46
smcginnisI added this one.19:46
smcginnisNot sure if folks saw, but there's been a lot of conversation on the ML and in the -tc channel about the idea of getting rid of the docs team.19:46
* tonyb missed the chatter but saw the reviews19:47
smcginnisAnd one idea raised was whether it made sense to move openstack-manuals under the release team since it is now just a coordinating spot for docs.19:47
smcginnisAnd there's just some procedural stuff that needs to happen around release time.19:47
smcginnisOther than some tooling that other folks sound willing to still maintain.19:47
smcginnisSo just wanted to raise it here to get folks thinking about it, pro or con, in case that developed more.19:48
smcginnisI'm not sure what my opinion is yet. :)19:48
tonybI haven't checked the review, but I more or less said openstack-manuals should be owned by a project team, realeases the least worse19:49
diablo_rojo_phonI guess it kinda makes logical sense to live under us.19:49
ttxIf the mainenance needed is all around release cycles, then yes it makes sense19:50
tonybI know we have items around release time that we corordinate with them, but that isn't all of it19:50
smcginnisI think I'd like to understand a little more of what that team currently does throughout the cycle to make sure we don't sign up for too much should the existing docs folks get pulled away.19:50
tonybfor example I recent;y added the EM SIG to the site19:51
diablo_rojo_phonCould make them like a sub team?19:51
tonybthat's very "not releases", and I'd be pretty uncomfortable owning that side of things19:51
diablo_rojo_phonsmcginnis +119:51
tonybso as long as we can keep some of the existing core team ...19:51
*** pcaruana has quit IRC19:52
ttxyes I feel like I'm missing details on what it would take to handle that19:52
tonybokay, so who wants to run that investigation?19:52
* tonyb kinda looks at TC memebers ;P19:53
tonyboh look we have a few of those ;P19:53
ttxI think dhellmann has a better understanding than most of what is involved19:53
ttxand we need to make a decision soon enough19:53
smcginnisI think I'm leaning towards rather still having a docs team and stepping in if Stephen just doesn't want to be the PTL for it.19:53
clarkbNot to interrupt but I wanted to mention that gerrit replication has caught up so it should be safe to do release work again (thank you for your patience)19:53
smcginnisclarkb: Thanks!19:54
tonybclarkb: \o/19:54
tonybI'd rathre keep the docs team too but that doens't seem to the be the direction the docs team is going19:55
ttxok no time left so let's iterate on that review19:56
tonyblast item shoudl be quick19:57
tonyb#topic meeting next week19:57
*** openstack changes topic to "meeting next week (Meeting topic: releaseteam)"19:57
tonybmany of y'all are in BCN next week and I assume will not be wanting to have an IRC meeting at 2000 on Thursday19:57
smcginnisMost of us will be out.19:57
tonybso cancel it?19:57
*** radeks_ has quit IRC19:58
tonybthat has the benfit that I get an extra hours sleep ;P19:58
smcginnisThen I'm in favor of cancelling. :)19:58
tonyby'all can have an in bar^wperson meeting instead19:58
ttxyes cancel19:58
ttxI'll be on a plane anyway19:59
tonybokay I think we're done here19:59
evrardjpthanks everyone19:59
ttxthe sort of plane that does not have wifi19:59
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at"20:00
openstackMeeting ended Thu May 16 20:00:00 2019 UTC.  Information about MeetBot at . (v 0.1.4)20:00
openstackMinutes (text):
tonyb#nailed it20:00
tonybThanks everyone20:00
diablo_rojo_phonThanks tonyb :)20:00
smcginnisWow, nice! "May 16 20:00:00 2019 UTC"20:01
smcginnisMilitary precision.20:01
tonybI am unreasonably pleased with those timestamps20:01
tonyb... now coffee20:02
diablo_rojo_phonThat's quite impressive20:02
*** armstrong has quit IRC20:03
smcginnisAnyone else want to take a look at that monasca release, or should I just approve it?20:03
tonyb[m]I'm happy for you to just approve it20:04
tonyb[m]I think I'm the owner so probably shouldn't anyway20:04
smcginnisI've made updates too, but think we're OK. I'll hit the button.20:05
*** whoami-rajat has quit IRC20:05
tonyb[m]Thanks smcginnis20:06
openstackgerritSean McGinnis proposed openstack/releases master: Drop project FF from train schedule FF week
*** e0ne has joined #openstack-release20:10
dhellmannsorry, I had to step away20:12
dhellmannthe instructions for the documentation end-of-cycle tasks is at
*** e0ne has quit IRC20:12
smcginnisdhellmann: Are there other tasks throughout the cycle that need to be done? Other than just maintaining the tooling?20:13
dhellmannnothing formal as far as I know, but we should ask stephenfin to be sure that hasn't changed20:13
smcginnisIf it becomes a SIG or something like that, then I think it's fine for the release team to take ownership of the steps listed there. But if the discussion goes down the full ownership by the release team route, then I would just want to make sure we wouldn't be signing up for more than would make sense for this team.20:14
dhellmannyeah, my proposal is just that we find some team to own the web site, and move all of the documentation in that repo to the sig20:15
dhellmannI'll make that clearer in a comment on the governance patch20:15
smcginnisThat sounds like a reasonable approach.20:15
openstackgerritMerged openstack/releases master: [monasca] final releases for pike
tonyb[m]dhellmann:  sounds good.  Thanks20:18
*** diablo_rojo has joined #openstack-release20:48
*** armax has quit IRC20:55
*** trident has quit IRC20:59
*** trident has joined #openstack-release21:00
*** mriedem has quit IRC21:53
*** armax has joined #openstack-release21:55
*** tosky has quit IRC21:59
*** jtomasek has quit IRC22:33
*** ekcs has quit IRC22:40
*** mlavalle has quit IRC22:44
openstackgerritSean McGinnis proposed openstack/releases master: [monasca] create pike-em tag against final releases
openstackgerritSean McGinnis proposed openstack/releases master: [tricircle] create pike-em tag against final releases
openstackgerritMerged openstack/releases master: [Puppet OpenStack] final releases for pike
*** diablo_rojo has quit IRC23:24
*** diablo_rojo has joined #openstack-release23:52

Generated by 2.15.3 by Marius Gedminas - find it at!