15:00:03 <smcginnis> #startmeeting releaseteam
15:00:04 <openstack> Meeting started Fri Jun 29 15:00:03 2018 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:07 <openstack> The meeting name has been set to 'releaseteam'
15:00:12 <smcginnis> Ping list: dhellmann, dims, fungi, tonyb, lbragstad, ttx, armstrong, annabelleB
15:00:17 <annabelleB> o/
15:00:20 <fungi> heyhowdy
15:00:24 <dhellmann> o/
15:00:25 <ttx> o/
15:00:46 <smcginnis> #link https://etherpad.openstack.org/p/rocky-relmgt-tracking Agenda
15:00:51 <smcginnis> dhellmann: Made it back already?
15:01:04 <dhellmann> yeah, I was being overly cautious
15:01:23 <smcginnis> Reasonable when it comes to those things. ;)
15:01:25 <smcginnis> #topic Tempest plugin deliverables
15:01:29 <dhellmann> one never knows
15:01:50 <smcginnis> There has been the ML discussion started by gmann on tagging the tempest plugins.
15:02:06 <smcginnis> dhellmann has posted a patch adding deliverable files for that
15:02:16 <smcginnis> #link https://review.openstack.org/#/c/578141/
15:02:44 <smcginnis> #link http://lists.openstack.org/pipermail/openstack-dev/2018-June/131810.html
15:03:08 <ttx> I think it merged ?
15:03:19 <smcginnis> I wanted to bring up here in case anything further was brought up on that thread, but I think questions have been answered.
15:03:38 <smcginnis> Yes, that's merged, and I think I saw another patch adding one that was missed last night.
15:03:49 <smcginnis> So probably not too much to talk about.
15:03:58 <dhellmann> ah, yes, ec2-api
15:04:06 <smcginnis> The one question I thought of that I didn't think we would want to add on the ML thread was deadlines.
15:04:32 <smcginnis> I see someone added a note to the etherpad about forcing tags, but my question was actually slightly different.
15:04:49 <smcginnis> We have the non-client lib freeze, which these kinda sorta are but not really.
15:05:00 <smcginnis> So what should be our deadline for them. The final release?
15:05:22 <smcginnis> I could see neeing to make test modifications up until the end.
15:05:57 <dhellmann> we should also talk about whether it's too late to add ec2-api to rocky
15:06:11 <dhellmann> I added the note to the etherpad about forcing
15:06:43 <dhellmann> I expect we want to leave the test libraries to the RC1 point as a final deadline, since projects may be adding tests up to that time
15:06:47 <smcginnis> Was the ec2-api patch adding more than just the tempest plugin? I haven't had a chance to look at it yet.
15:06:57 <dhellmann> yeah, it adds ec2-api as a cycle-with-milestone project
15:07:16 <smcginnis> We are past milestone 2, so I would say no on that one.
15:07:22 <smcginnis> At least that has been our policy.
15:07:29 <dhellmann> it has, yeah
15:08:12 <dhellmann> so my suggestion for a deadline is the rc1 branch point, and we tag and branch at the same time
15:08:24 <dhellmann> we can tag before and after, of course, but that's the point where we *need* a tag
15:08:25 <smcginnis> Have they been doing their own releases so far? I don't see any deliverables ever from them.
15:08:36 <dhellmann> they had been. they haven't released off of master in quite a while
15:08:44 <armstrong> @dhellmann: was the ex2-api added in the Queen release?
15:08:57 <dhellmann> they're not really following standard practices, so I expect we'll need to work with them some
15:09:43 <dhellmann> armstrong : we do not have any data for them in the openstack/releases repo at all
15:09:55 <dhellmann> they do have tags and some branches, so they've been releasing, just not using our processes
15:09:57 <smcginnis> #info Tempest plugins will have a release deadline of RC1 at which point release team will force a tag and branch if not requested by project.
15:09:58 <armstrong> Ok I see
15:10:30 <dhellmann> stable/queens looks like it has 6.0.0 as a version but master has 3.0.0
15:10:40 <dhellmann> so my guess is they are branching and then releasing, instead of the other way around
15:11:01 <smcginnis> Should we suggest independent for ec2-api for now, then pick them up in stein? Or recommend they do what they have been doing and start with stein-1?
15:11:17 <dhellmann> I think ttx fixed their ACLs so we're going to have to do something for them
15:11:22 <smcginnis> Ah
15:12:01 <dhellmann> yeah, I don't see any tagging permissions in gerrit/acls/openstack/ec2-api.config
15:12:21 <smcginnis> And looks like they came under governance three years ago.
15:12:32 <dhellmann> they've always been a bit of an outlier
15:12:43 <smcginnis> Extracted from nova: https://github.com/openstack/governance/commit/2d44cc04f69f8168b052d59fbfd1d5ba2a40ce53
15:13:33 <smcginnis> So we either need to do independent for now, or allow them to be part of the cycle even though they've missed two milestones.
15:13:38 <ttx> or drop it
15:13:44 <smcginnis> True
15:13:46 <dhellmann> I'm not sure why they want the milestone release model, the only milestone tag they have is 0.1.0-rc1
15:14:11 <smcginnis> I would think the service would be tied to a given release though.
15:14:29 * smcginnis doesn't actually know much about ec2-api though
15:14:33 <dhellmann> I guess?
15:14:36 <ttx> Was the healthcheck done ?
15:14:52 <dhellmann> not yet
15:14:58 <ttx> We could ask whoever is assigned to them to prioritize up
15:14:58 <dhellmann> TheJulia and cmurphy are signed up for that
15:15:01 <smcginnis> I don't see it.
15:15:06 <dhellmann> #link https://wiki.openstack.org/wiki/OpenStack_health_tracker#Oslo
15:15:10 <dhellmann> #undo
15:15:13 <dhellmann> #link https://wiki.openstack.org/wiki/OpenStack_health_tracker
15:15:29 <ttx> Like I'd like to know how functional it is and if it has users, before putting any  effort on it
15:15:39 <dhellmann> I'll contact TheJulia and cmurphy
15:15:41 <ttx> It's sufficiently peripheral that it's an easy cleanup
15:16:00 <smcginnis> ACtivity so far this cycle looks to be mostly "administrative" changes, but there are a couple functional changes.
15:18:12 <smcginnis> Let's hold on this for now. I don't think we can make any decisions in this meeting for the project.
15:18:20 <smcginnis> I think it will require a little investigation first.
15:22:28 <ttx> also how current it is with Amazon's API
15:22:28 <ttx> I just have no idea :)
15:22:28 <fungi> i've always wondered that
15:22:28 <fungi> same for the s3 compat layer
15:22:28 <ttx> I remember when I worked on Eucalyptus, keeping up with AWS API was kind of a challenge :)
15:22:28 <smcginnis> Given the activity there, I would assume it is not current with the upstream API.
15:22:28 <smcginnis> OK, let's defer that conversation until later.
15:22:28 <dhellmann> smcginnis , ttx : would one of you record our questions about the team as concerns in the health check wiki page?
15:22:28 <smcginnis> dhellmann: I can do that.
15:22:28 <dhellmann> thanks
15:22:28 <smcginnis> I also put my name down as a follow up task in our etherpad.
15:23:21 <smcginnis> And to make it easier for folks to get to the actual output - http://logs.openstack.org/94/575794/1/check/build-openstack-sphinx-docs/b522825/html/stein/schedule.html
15:24:13 <dhellmann> I sent email to TheJulia and cmurphy, cc-ing smcginnis
15:24:32 <smcginnis> ack
15:24:44 <TheJulia> ack, I've not seen it yet but I'll go look
15:24:51 <dhellmann> TheJulia : thanks
15:24:53 <smcginnis> TheJulia: Thanks
15:26:43 <dhellmann> have we had any feedback about the schedule from outside the team?
15:26:46 <smcginnis> ttx: Any updates on the schedule planning from your end? Otherwise I don't really have much to add other than making sure folks saw the patch to take a look at what it might look like.
15:26:55 <smcginnis> dhellmann: Nothing that I've heard.
15:27:09 <smcginnis> From a couple conversations, folks are just waiting to see what is decided I think.
15:27:20 <smcginnis> Or for a more specific proposal to the ML.
15:27:26 <dhellmann> was there a ML thread? yeah -- I couldn't remember
15:27:53 <ttx> it's more and more likely that the event will happen in Denver in Spring
15:27:59 <ttx> (PTG)
15:28:12 <smcginnis> All Denver, all the time.
15:28:24 <smcginnis> Works great for me. :)
15:28:25 <ttx> I heard that the venue supports us running the PTG on the Saturday
15:28:26 <fungi> no matter where you go, you're always in denver
15:28:42 <ttx> Nothing signed, but things looking good on that side
15:28:58 <ttx> so doing 3+3 days
15:29:00 <smcginnis> Oh great, the question of back to back or overlap was one of the important things in my mind.
15:29:06 <dhellmann> should we start asking people to check the deadlines against their favorite holidays?
15:29:20 <ttx> I like that it stresses that the events are separate
15:29:24 <smcginnis> ++
15:29:31 <ttx> yes, I think we can float it
15:29:39 <smcginnis> What's the next step. Mailing list post?
15:29:47 <smcginnis> I think that would need to come from you ttx ^
15:29:53 <ttx> maybe mention it in the weekly post ?
15:30:08 <smcginnis> Yeah, I'll add it to the next one.
15:30:25 <ttx> We'll do a sepaarte post once we are ready to commit
15:30:36 <ttx> hopefully two weeks from now
15:30:37 <smcginnis> I think it might be good to have its own thread before then to vet it?
15:31:36 <ttx> your call
15:31:36 <dhellmann> the final date is tied to the event, but we can adjust the deadlines in the middle of the cycle
15:32:10 <ttx> i can do a thread next week if you prefer
15:32:28 <ttx> But i fear that will turn into a PTG love/hate discussion
15:32:29 <smcginnis> OK, I'll add it to the countdown. We'll see if that gets enough attention
15:32:37 <smcginnis> ttx: That is a very valid concern.
15:32:37 <ttx> befroe we are 100% sure that will happen
15:33:10 <smcginnis> ttx: I'll put something in the countdown draft and probably ask you to take a look and make sure it's OK.
15:33:16 <ttx> ++
15:33:24 <armstrong> The PTG is happening in September right?
15:33:37 <ttx> Oh yes, we are talking about the one in Spring 2019
15:33:45 <ttx> to define teh Stein cycle
15:34:15 <smcginnis> armstrong: Normally it would be late February like Dublin was, but with changing the events we would change the cycle duration to align with it.
15:34:34 <annabelleB> I mean, we have to commit to a cycle schedule, ptg future unknown, so cycle comments only! :)
15:34:36 <armstrong> @ttx ok I got it now
15:35:54 <armstrong> @ttx: thanks, will kept that in mind
15:36:06 <smcginnis> #topic Open Discussion
15:36:13 <smcginnis> That's all I had on the agenda.
15:36:19 <smcginnis> Anything else we should cover?
15:36:42 <fungi> release-tools retirement changes are up for review
15:36:46 <fungi> #link https://review.openstack.org/#/q/topic:retire-release-tools
15:36:47 <smcginnis> annabelleB: Need anything from me for adding release highlights info?
15:36:52 <smcginnis> fungi: ++
15:36:54 <smcginnis> Thanks
15:37:13 <annabelleB> smcginnis: haven’t gotten to that draft yet, but on my list for today or first part of next week
15:37:18 <fungi> the project-config and governance changes will need your +1 smcginnis
15:37:33 <smcginnis> annabelleB: Great, just ping me if you need anything I can help with.
15:37:42 <annabelleB> will do! thanks!
15:37:49 <fungi> also a draft announcement to the dev ml is available if someone wants to fact-check it before i send:
15:37:51 <fungi> #link https://etherpad.openstack.org/p/release-tools-retirement
15:37:57 <smcginnis> fungi: I got one of them, but will make sure I track them all down.
15:38:43 <dhellmann> fungi : email lgtm
15:39:06 <fungi> thanks! i'll fire it off after the meeting
15:39:40 <cmurphy> I can start reaching out to ec2-api on monday unless TheJulia wants to get to it first
15:40:10 <dhellmann> cmurphy : thanks!
15:40:12 <smcginnis> Just a reminder, I will be on vacation in two weeks and might try not to bring my laptop.
15:40:22 <ttx> ++
15:40:36 <TheJulia> The earliest I would be able to is monday as well
15:40:41 <dhellmann> annabelleB : my notes from our review training session finally made it into the docs: https://review.openstack.org/#/c/579019/
15:40:42 <dhellmann> smcginnis : I recommend not bringing it :-)
15:40:51 <smcginnis> cmurphy, TheJulia: Thanks for doing that.
15:41:01 <annabelleB> dhellmann: I’ll check that out!
15:41:07 <smcginnis> dhellmann: It might be hard to do, but I'm going to try. ;)
15:41:25 <dhellmann> smcginnis : I don't even like to bring a tablet with me any more. The fewer screens on vacation, the better I do
15:41:53 <smcginnis> I'm getting to the point where that sounds like very good advice.
15:42:12 <smcginnis> OK, anything else today?
15:42:37 <smcginnis> Alrighty then, thanks everyone.
15:42:53 <dhellmann> o/
15:42:58 <smcginnis> #endmeeting