Wednesday, 2016-03-16

*** mriedem has joined #openstack-release00:01
*** sdake has quit IRC00:01
*** dims has joined #openstack-release00:08
*** sdake_ has quit IRC00:08
*** sdake has joined #openstack-release00:11
*** armax has joined #openstack-release00:14
*** sdague has joined #openstack-release00:22
*** openstack has joined #openstack-release00:24
*** sdague has quit IRC00:26
*** sheeprine has quit IRC00:30
*** sheeprine has joined #openstack-release00:34
*** dims has joined #openstack-release00:45
*** david-lyle has joined #openstack-release01:04
*** dims has quit IRC01:07
*** dims has joined #openstack-release01:12
*** dims has quit IRC01:29
*** dims has joined #openstack-release01:29
*** mriedem has quit IRC01:42
*** dims has quit IRC01:52
*** dims has joined #openstack-release01:56
*** dims has quit IRC02:03
*** dims has joined #openstack-release02:05
*** amrith is now known as _amrith_02:24
*** sridhar_ram has joined #openstack-release02:31
*** sridhar_ram has quit IRC02:41
*** dims has quit IRC03:37
*** cody-somerville has quit IRC03:46
*** cody-somerville has joined #openstack-release04:01
*** cody-somerville has quit IRC04:01
*** cody-somerville has joined #openstack-release04:01
*** sdake has quit IRC04:50
openstackgerritTony Breeds proposed openstack-infra/release-tools: add convenience script for finding unreleased stable branch changes
*** sridhar_ram has joined #openstack-release05:31
openstackgerritMerged openstack-infra/release-tools: Actually use the URL specific in --project-list
*** sridhar_ram has quit IRC05:42
*** david-lyle has quit IRC05:45
*** david-lyle has joined #openstack-release05:45
skraynevttx: hi. I can not find a tag stable-mitaka-backport potential. will it be added after creating stable branch or you can do it before? I just wanted to move out some bugs from rc1 with marking them with this tag. Also I am wondering about creating mitaka-rc1, Do we need do some patch to releases repo for it?06:17
*** ihrachys has joined #openstack-release07:04
openstackgerritIhar Hrachyshka proposed openstack/releases: Neutron Mitaka RC1 deliverables
*** ihrachys has quit IRC07:06
*** AJaeger has joined #openstack-release07:21
AJaegerrelease team, reports an error with with freezer-web-ui with incompatible requirements...07:22
ttxdhellmann: yes07:38
ttxskraynev: Launchpad tags can be freely added07:39
ttxi.e. you can put anything you want and ignore autocompletion07:40
ttxbut if you want it to appear in autocompletion you should add it to teh heat official tags:07:40
ttxHeat drivers group in Launchpad should have the rights to update those07:41
*** amotoki has joined #openstack-release07:46
*** ihrachys has joined #openstack-release08:04
skraynevttx: got it. thank you for the link.08:07
openstackgerritIhar Hrachyshka proposed openstack/releases: Neutron Mitaka RC1 deliverables
skraynevttx: what about rc1 related question? do we need propose patch to releases repo?08:08
openstackgerritIhar Hrachyshka proposed openstack/releases: Neutron Mitaka RC1 deliverables
ttxskraynev: you mean the Launchpad milestone ?08:09
ttxyou can create it yourself too08:09
ttxIf you mean the *git* tag, then yes it requires a change to openstack/releases and we'll handle it08:10
ttxbut you can create the "mitaka-rc1" milestone on alright08:11
skraynevttx: I meant the second, i.e. "git" tag. Is the last date for this is tomorrow? So if I propose patch today's evening or tomorrow's morning, it's ok ?08:12
ttxskraynev: the target date is this week, yes. But if it's not ready and you still have release-critical bugs, you could delay08:15
ttxThere is no point in tagging the RC1 if you know it's broken08:15
ttxand request a RC2 Monday08:15
ttxbut if you covered all the release-critical stuf, yes, tagging tomorrow is fine08:16
skraynevttx: I thought, that we may propose rc1 on this week and if it will be necessary do rc2 on the next or it's wrong approach?08:21
ttxsure that is fine08:21
ttxeverything is in the "if it will be necessary"08:22
ttxif you already know it will be necessary to do RC2 next week there is little point in doing a RC1 this week08:22
ttxBut if you think the RC1 is looking good enough for now, then yes tag this week!08:22
ttxAnd tag RC2 next week if necessary08:23
ttxhoping I make sense08:23
ttxskraynev: ^08:25
skraynevttx: more than need ;) thank you very much for detailed explanation. it is that I wanted to hear08:34
*** ig0r_ has quit IRC08:39
*** kzaitsev_mb has joined #openstack-release09:24
*** dtantsur|afk is now known as dtantsur09:42
*** sdague has joined #openstack-release09:43
*** amotoki has quit IRC09:43
*** dims has joined #openstack-release09:51
*** openstackgerrit has quit IRC09:53
*** openstackgerrit_ is now known as openstackgerrit09:53
*** openstackgerrit has quit IRC09:53
*** openstackgerrit_ has joined #openstack-release09:53
*** openstackgerrit_ is now known as openstackgerrit09:54
*** openstackgerrit_ has joined #openstack-release09:55
*** openstackgerrit has quit IRC09:55
*** openstackgerrit has joined #openstack-release09:56
*** sdague has quit IRC10:00
*** sdague has joined #openstack-release10:03
*** sdague has quit IRC10:11
*** sdague has joined #openstack-release10:11
*** daemontool has joined #openstack-release10:28
dimsttx : +10000 to "In an ideal world you'd either grow the resources / bandwidth"10:36
*** dims has quit IRC10:53
*** dims has joined #openstack-release10:59
*** kzaitsev_mb has quit IRC10:59
*** _amrith_ is now known as amrith11:16
*** openstackgerrit has quit IRC11:18
*** openstackgerrit has joined #openstack-release11:18
*** dtantsur is now known as dtantsur|brb11:34
*** ihrachys has quit IRC11:42
*** gordc has joined #openstack-release11:44
*** kzaitsev_mb has joined #openstack-release11:44
sdagueI want to live in theory, everything works in theory :)11:50
dimsLOL sdague11:51
*** dtantsur|brb is now known as dtantsur12:01
*** kzaitsev_mb has quit IRC12:24
*** kzaitsev_mb has joined #openstack-release12:25
*** pcaruana has quit IRC12:28
dimsThierryland? :)12:46
ttxyep sounds a lot like that12:46
ttxThe land where devs have no idea what to do next and look up wishlist bugs list for inspiration12:47
ttxdhellmann: we have the ACLs merged, so processing RC1s is a go12:54
ttxhappy to help in the coming hours12:54
dhellmannttx: sounds good. I'm just getting started, do you want to do the neutron tag? they were a bit impatient to have their branch created so they could sprint on something.12:57
ttxdhellmann: anything special I should watch for ? Just planned on running the tag (from_yaml) and then create stable branch12:59
ttx./ and ./make_stable_branch.sh13:00
dhellmannttx: that should do it13:00
ttxalright let's try13:00
dhellmannit'll be interesting to see how works for you13:00
dhellmannI'm not sure anyone else has run that yet13:00
dhellmannsince we added the reno patch logic13:00
ttxhmm, we might want armax or mestery to sign off on Ihar's SHAs13:02
ttxdhellmann: or are you comfortable with those ?13:02
patchbotttx: patch 292445 - releases - Neutron Mitaka RC1 deliverables13:02
ttxdoing glance in the mean time13:02
dhellmannoh, I hadn't noticed ihar had updated the patch, yeah, we should probably get mestery to sign off13:03
ttxdhellmann: for make_stable_branches, I should run something like ./ mitaka openstack/glance ?13:05
dhellmannttx: yes, that's right13:05
dhellmannwell, "branch" not "branches"13:05
ttxok, let's see how it goes13:05
dhellmannand you have to run it for all the repos, so neutron will need 4 calls -- we should write a make-branches-from-yaml script13:06
ttxdhellmann: haven't reviewed the reno cache stuff yet, wanted to give it review justice13:07
*** bdemers has joined #openstack-release13:11
dhellmannttx: sure. it needs more tests, I'll try to get back to that later this week13:12
*** kro_sinus_hell is now known as krot_sinus_purga13:15
*** krot_sinus_purga is now known as kro_sniffles13:15
*** smcginnis_away is now known as smcginnis13:15
openstackgerritMerged openstack/releases: Tag Glance Mitaka RC1
openstackgerritMerged openstack-infra/release-tools: Add update_reviews tool
ttxdhellmann: worked alright. Maybe an extra space in
patchbotttx: patch 293415 - glance - Update reno for stable/mitaka13:20
ttxalso maybe would make sense to place mitaka first in that file13:21
*** ig0r_ has joined #openstack-release13:24
ttxadditionally I'll manually send a "RC1, master now open for newton" canned email for the things I process today13:24
dhellmannyeah, every project has different whitespace there, so that's going to need to be made much smarter13:24
ttxdoes the order matter ?13:25
dhellmannnot really13:25
ttxok good, also I epect the extra space to not hurt, just look ugly13:25
dhellmannthe extra space will actually cause it to fail to parse, so we'll have to fix those13:26
ttxah, will manually fix13:26
dhellmannyeah, for the libraries I asked the owning project liaisons to fix them but we have a lot fewer of these so we should be able to fix them ourselves to make them land more quickly13:27
*** mriedem has joined #openstack-release13:28
*** sdake has joined #openstack-release13:33
dhellmannttx: via stevemar in -infra13:34
dhellmannit seems to me like we have a hole in the test jobs for that repo if we can land a constraint that doesn't match the requirement spec13:34
dhellmannlike we're not actually trying to install everything, and just relying on the dsvm job to do that13:34
ttxgoo thing nobody uses that13:34
dhellmannapparently it broke something, discussion in -infra13:35
*** doug-fish has quit IRC13:39
*** doug-fish has joined #openstack-release13:42
dhellmannttx: I'm going to self-approve the reno fix for deleted notes so we can release that today13:45
*** doug-fish has quit IRC13:46
openstackgerritMerged openstack/reno: handle deleted notes properly
openstackgerritMatt Riedemann proposed openstack-infra/release-tools: add convenience script for finding unreleased stable branch changes
*** mriedem is now known as mriedem_meeting13:54
*** armax has joined #openstack-release13:54
armaxdhellmann: ping13:58
dhellmannarmax : pong13:58
dhellmannarmax : I see you've +1ed the rc1 tag patch, we were waiting for that before processing it13:59
armaxdhellmann: re
patchbotarmax: patch 292445 - releases - Neutron Mitaka RC1 deliverables13:59
armaxdhellmann: yes13:59
armaxdhellmann: we still have one or two fixes we’d like to land14:00
dhellmannarmax : do you want to hold rc1, or are you planning an rc2?14:00
*** doug-fish has joined #openstack-release14:00
armaxdhellmann: that’s the part I am unsure of, whether we have a little extra time to pull the trigger on rc114:00
armaxdhellmann: or we can simply go ahead with this one, but plan for an rc214:00
*** doug-fish has quit IRC14:01
*** doug-fish has joined #openstack-release14:01
dhellmannarmax : you have this week, so if you have the fixes in the queue you could wait14:01
armaxwait and bump the hash for rc1 you mean?14:02
ttxarmax: better wait totag rather than tag already knowing you'll do an rc2 the next day14:02
armaxttx: fair point14:02
armaxI was not sure if you guys rather tagged mid week than later in the week14:02
ttxit's supposed to be a release candiadte. Even if it's extremely likely that you'll do another RC, it should be < 100%14:03
armaxbut ideally I’d open master if I can14:03
dhellmannttx: is it better to get a tag this week, or wait until next week?14:03
ttxdhellmann: it's a bit of a trade-off. You don't want to communicate that RCs are useless14:03
ttxsince you kinda want people to test and package them14:04
ttxbut on the other hand you want a RC1 asap14:04
dhellmannok, so the deadline for an rc isn't as firm as I had been treating it14:04
ttxyes, this week is a target week14:04
dhellmann"target" not "deadline"14:04
ttxif some projects miss it and are not ready, it's not that bad14:04
dhellmannok, that makes sense14:04
ttxdifferent from the mitaka-3 deadline where we define a point in time14:04
ttxhere we define readiness14:04
ttxbut it's still good to be firm and for people missing the target date to be seen as a problem, otherwise you just give procrastinators an extra week14:05
ttxso it's a bit of a balancing act14:05
* dhellmann feels wobbly14:06
dhellmannok, armax please -1 the proposed rc1 if you want to hold off. I'm going to step away for a bit but I'll check back in shortly.14:06
*** sigmavirus24_awa is now known as sigmavirus2414:06
armaxttx, dhellmann: this is a bit of a moving target and knowing when to shoot it down it’s the fine balance we need to strike14:06
ttxdhellmann: in previous cycles we had extra legroom because we could cut the branch before th RC1, but we decided that was extra complexity14:06
ttxand it can be counterproductive, since "opening newton" is the carrot we have to encourage people to finish rc114:07
ttxso I'm fine tagging RC1 as soon as there is a remote possibility that RC1 could be the end release. Because after all, we'll promote the RC1 if that is the only thing we have on release day14:08
ttxremote can be 1%14:08
ttxbut as long as it's 0.00% I think we should wait14:08
ttxotherwise we are wasting everyone's time14:08
armaxdhellmann, ttx as far as I am aware, our RC1 is sound, the patch we want to land fixes a performance issue14:09
ttxarmax: so you could tag RC1 and include that patch in a future RC if one ends up being desirable14:09
armaxsomething we’ll have to backport even if it didn’t make it14:09
armaxttx: right, I was operating under that assumption14:09
ttxi.e. not consider that patch a release critical issue, but include it together with the next release-critical issue you find14:10
ttxall depends on what you call release-critical obviously14:10
armaxttx: that we could give ourselves the chance to land that in an RC2 if some other catastrophic issue shows up14:10
ttxwhich will happen in 99% of the cases14:10
ttxbased on history14:10
ttxarmax: so yeah, you decide14:11
ttxdepends a lot on how usable the thing is without the patch14:11
armaxttx: ok, I give myself the end of today14:11
armaxwhat’s in is in, what’s out is out14:11
* ttx holds on14:11
ttxdhellmann: I'll send the Glance RC1 manual announce then, might trigger others14:12
armaxdhellmann, ttx thanks for the clarifying comments14:13
ttx#success Glance is the first project to issue a RC1 !14:18
openstackstatusttx: Added success to Success page14:18
dimsgo glance!14:19
*** sdake has quit IRC14:27
openstackgerritSergey Kraynev proposed openstack/releases: Tag Heat RC1 Mitaka
*** mriedem_meeting is now known as mriedem14:56
ttxskraynev: alright, on its way !15:07
skraynevttx: we decided to move 5 bugs to rc2.15:08
dhellmannttx: when you're done, I'll do the tacker liberty release15:08
ttxdhellmann: ack15:08
openstackgerritMerged openstack/releases: Tag Heat RC1 Mitaka
*** david-lyle has quit IRC15:15
*** david-lyle has joined #openstack-release15:15
ttxdhellmann: ew. :)15:16
patchbotttx: patch 293496 - heat - Update reno for stable/mitaka15:16
ttxdhellmann: all done for heat RC115:17
dhellmannttx: yeah, my bash patch logic is pretty dumb. :-/15:17
ttxdhellmann: not blaming or anything, just another case to handle15:17
dhellmannyeah, that's all going to have to be rewritten to be much smarter15:17
ttxlooks like we have a wide variety of those15:18
* dhellmann starts the tacker 0.2.0 release15:18
openstackgerritMerged openstack/releases: Release tacker 0.2.0 for liberty
openstackgerritDoug Hellmann proposed openstack/releases: reno 1.6.1
*** sdake has joined #openstack-release15:25
* dhellmann steps away for a bit15:28
*** david-lyle_ has joined #openstack-release15:34
*** david-lyle has quit IRC15:34
*** jroll has quit IRC15:41
*** jroll has joined #openstack-release15:41
*** jroll has quit IRC15:41
*** jroll has joined #openstack-release15:41
*** sridhar_ram has joined #openstack-release16:03
* dhellmann returns16:11
amrithdhellmann, just replied to your question in Sorry I didn't see it till now.16:15
patchbotamrith: patch 292650 - releases - Please tag python-troveclient v2.2.016:15
openstackgerritArmando Migliaccio proposed openstack/releases: Neutron Mitaka RC1 deliverables
*** david-lyle_ is now known as david-lyle16:20
dhellmannamrith : I see changes to existing stuff in
amrithdhellmann, the meat of the change is in troveclient/v1/, and They add new capabilities. There are new tests proposed, a new utility function proposed in, and a new parameter with a default of None to an exception that existed below.16:25
amrithyes, some existing files are being modified16:25
dhellmannamrith : I'm sorry. The freeze is an important part of stabilizing things, and we've told other projects with a similar situation "no" as well. Your best course for now is to finish the mitaka work on the service, prepare a release candidate, and put the client changes off until newton opens.16:26
amrithbut the API's (adding modules to create with a None, for example) are not compatibility issues. I think.16:26
amrithdhellmann, this was something we'd specifically requested as part of the FFE earlier. why does the client change have to wait for newton, can't we request a new client once rc1 is frozen?16:27
amrithoh, sorry16:27
amrithyou said newton opens16:27
dhellmannwe treat all libraries the same way during this period: critical issues only for releases16:27
amrithOK, I think we can live with that. Not ideal, but I don't think that's as bad as it sounded when I first read.16:27
amrithunderstood. I'll remember for next time that FFE's don't extend to the client side. That freeze is a hard freeze.16:28
amriththanks, I think we can make taht work.16:28
dhellmannyeah, you're not the only project in this state so we'll be doing more next cycle to communicate about the freeze16:28
amrithok to keep the review around and just request it again once newton is open?16:28
amrithI'll -2 it for now ...16:28
amrithwell, I can't -2 it, I'll wf -1 it.16:29
dhellmannamrith : you'll need to update it to move the file to the newton directory, since the new release will be part of newton not mitaka16:29
dhellmannwell, not move the file, but make a new file with this request in it16:29
amrithcan I request upper-constraints be increased for mitaka at a later time?16:29
amrithright now, upper-constraints for mitaka says 2.1.116:30
dhellmannamrith : no, that's going to be frozen, too, at least until we sort out backwards-compatibility testing16:30
amriththat means that if we have even a bugfix, then we can't release it for mitaka.16:30
dhellmannwell, bug fixes will be allowed, but not feature releases16:30
dhellmannI thought you were asking specifically about allowing this new feature into mitaka16:30
amriththe feature is partially in mitaka16:31
amrith(the server side)16:31
amrithyou could get to it on the REST API16:31
amrithall that we're asking here is for the client side of that change16:31
dhellmannthat's fine16:31
dhellmannno, you're asking me to break the rules all of the other projects are following16:31
amrithbecause when we FFE'ed this, we assumed that the FFE extended to the client.16:31
dhellmannwell, I thought I made clear that client libraries were frozen16:32
amrithsorry, no. I agree, I don't want to talk about this FFE'ed new feature in Mitaka client.16:32
amriththat, we agree about.16:32
amrithmy question is about a bug fix in Mitaka.16:32
amrithsuppose we need a 2.1.216:32
amrithwhat then?16:32
amriththat, I hope would be OK16:32
amrithnot this FFE'ed feature. I agree, 2.2.0 is a newton thing.16:32
dhellmannafter the stable branch is created for the requirements repo, we will allow updates for bug-fix releases from mitaka branches of libraries to go into the constraints file. we won't raise the constraints to include new features until we have better backwards-compatibility testing in place. we won't be applying automatically-generated updates to the constraints file.16:33
amrithOK, all good then. Thanks. I'll -1 the changes and resubmit once newton opens.16:34
dhellmannok. we should go ahead and create your stable/mitaka branch for the client from the latest release, then16:34
dhellmannI have that recorded as 2.1.1, is that right?16:34
dhellmannamrith : ^^16:37
amriththat is correct dhellmann16:37
amrith2.1.1 is python-troveclient stable/mitaka.16:37
dhellmannamrith : ok, I'll go ahead and create your branch now16:37
amrithI sent you the version for trove-dashboard as well.16:38
amrithI will be merging final changes for openstack/trove today and should be able to tag the server side as well.16:38
dhellmannamrith :
ttxdhellmann: looks like I can process neutron now16:40
ttxdhellmann: if you don't use the baton16:40
amrithdhellmann, trove-dashboard is
patchbotttx: patch 292445 - releases - Neutron Mitaka RC1 deliverables16:41
dhellmannamrith : we will cut branches from the rc1 tags for projects following the milestone system, so you can submit the request for trove-dashboard and we'll create the branch when we process it16:41
dhellmannttx: I'm just about to do a reno release, give me a couple of minutes?16:42
*** kzaitsev_mb has quit IRC16:42
ttxdhellmann: standing by16:43
openstackgerritMerged openstack/releases: reno 1.6.1
* dhellmann passes the baton to ttx16:44
amrithdhellmann, thanks. If I understand that correctly, trove and trove-dashboard, submit change in openstack/releases/ (deliverables/trove.yaml and deliverables/trove-dashboard.yaml) with ...rc1 and an appropriate hash. yes?16:44
* ttx catches16:44
dhellmannamrith : yes16:44
amriththx, wilco16:44
sridhar_ramdhellmann: thanks for merging tacker 0.2.0. The next item in the tacker series is tackerclient 0.2.1 - please review when you get a chance.16:46
patchbotsridhar_ram: patch 291879 - releases - Release tackerclient 0.2.1 for liberty16:46
openstackgerritJohn Garbutt proposed openstack/releases: Tag Nova Mitaka RC1
openstackgerritMerged openstack/releases: Neutron Mitaka RC1 deliverables
johnthetubaguydhellmann: ttx: can I quickly check about how master opens for newton, now setup.cfg doesn't have a version number in it, and the last tag will still be mitaka?16:54
dhellmannjohnthetubaguy : sure, let me explain16:54
dhellmannjohnthetubaguy : we will create the stable/mitaka branch from the rc1 tag16:55
dhellmannafter that, patches to master need to be backported16:55
johnthetubaguyyep, that bits fine, thats normal16:55
*** kzaitsev_mb has joined #openstack-release16:55
dhellmannwe'll tag something on stable/mitaka as your final (either rc1, rc2, etc.)16:55
dhellmannthe version # comes from the tag, via pbr16:55
johnthetubaguyI just just wondering how we know masters is generating 14.x versions16:55
dhellmannthe work we did at the beginning of this cycle ensures that will all work properly16:56
johnthetubaguyI guess it doesn't till we do the first tag?16:56
dhellmannmaster and stable will have the same versions for some small period, but we decided that doesn't matter because CD folks should only one branch or the other16:56
dhellmannand it will be addressed more directly when we tag b1 for newton on master16:57
johnthetubaguyyeah, thats true, it doesn't matter too much16:57
johnthetubaguyOK, thanks, I am clear whats happening now16:57
dhellmannyep, thanks for checking in16:58
dhellmannttx, dims, sdague :
*** sigmavirus24 is now known as sigmavirus24_awa17:02
*** kzaitsev_mb has quit IRC17:14
dimsdhellmann : +117:16
ttxso the two things I do in addition to running the scripts is to check the tarball link on the releases page once it's built, and fixing the generated reno/mitaka review17:18
ttxand send the manual canned announcement replacing $project. That makes 317:19
*** dtantsur is now known as dtantsur|afk17:20
*** sridhar_ram1 has joined #openstack-release17:21
*** sridhar_ram has quit IRC17:22
ttxwe should probably approve the stable/mitaka .gitreview bumps ourselves since they end up in a release-controlled branch17:34
ttxarh, nova17:35
ttxdhellmann: shall I do nova or you'll handle it ?17:36
dhellmannttx: go for it, I'm on  a call17:36
dimsttx : go to those review and do a +2A? i can help17:37
*** armax has quit IRC17:37
ttxdims: thx17:37
*** johnthetubaguy_ has joined #openstack-release17:39
*** johnthetubaguy has quit IRC17:41
*** johnthetubaguy_ is now known as johnthetubaguy17:41
dimsttx : 3 reviews i did not see a +2 button
patchbotdims: patch 291338 - python-muranoclient (stable/mitaka) - Update .gitreview for stable/mitaka17:42
patchbotdims: patch 291799 - python-brick-cinderclient-ext (stable/mitaka) - Update .gitreview for stable/mitaka17:42
patchbotdims: patch 291328 - django_openstack_auth (stable/mitaka) - Update .gitreview for stable/mitaka17:42
dimssorry 2 reviews17:43
dimsopenstack/python-brick-cinderclient-ext and openstack/python-muranoclient17:43
ttxoh, that would be non-releae-controlled ones17:44
ttxdims: we only control the milestones/managed stuff17:44
ttxso not a big deal if we don't push the others17:44
*** kzaitsev_ip_ has joined #openstack-release17:45
*** sdague has quit IRC17:46
johnsomttx Has the clock run out on:
patchbotjohnsom: patch 290735 - governance - Update lbaas dashboard repo to be similar to octav...17:46
dimsttx done17:47
ttxjohnsom: close enough :)17:48
johnsomExcellent.  Thanks17:49
ttxjohnsom: approved17:49
*** kzaitsev_ip_ has quit IRC17:49
*** sdague has joined #openstack-release17:52
*** kzaitsev_ip_ has joined #openstack-release17:54
*** kzaitsev_ip_ has quit IRC17:57
openstackgerritSridhar Ramaswamy proposed openstack/releases: Release tacker 0.2.1 for liberty
*** sigmavirus24_awa is now known as sigmavirus2418:07
*** kzaitsev_mb has joined #openstack-release18:10
ttxdammit cloning nova takes forever with my 7pm bandwidth. I should really set up caching18:13
lifelessttx: or keep a cached copy?18:15
lifelessttx: e.g. ~/src/nova ?18:15
ttxlifeless: I mean for the release script. Enable zuul-cloner cache directory18:16
ttxit's probably just an env variable away18:17
ttxdhellmann: nova done.18:19
* ttx closes shop for today18:19
dimsgood night ttx18:20
dimsi +2A'ed the .gitreview18:20
AJaegerdims, dhellmann: So, do we have stable/mitaka now? In that case we should setup translations for stable/mitaka. right now the jobs only propose to master and we need to setup the branch in zanata...18:29
*** mriedem has quit IRC18:35
*** mriedem has joined #openstack-release18:38
stevemardhellmann: ttx dims you'll have a keystone rc1 release request in a few hours, the last few patches are merging18:40
dimsAJaeger :
dimsAJaeger : oops,
AJaegerdims, ok, time for translation setup for these projects...18:42
dimsstevemar : ack. i still haven't made any server releases, so dhellmann is the one you need as ttx has wrapped up for the day18:43
dhellmannAJaeger : we should talk about adding that to the branch script so it happens automatically18:44
dhellmannstevemar : are you ready for mitaka?18:45
sdaguedhellmann: when do we branch requirements for stable/mitaka18:45
dhellmannstevemar : nevermind, I see your comment in the scrollback  now18:45
stevemardhellmann: soon, got 4 patches going through merge18:45
dhellmannsdague : I think in the past we've done that after all of the server projects have branched, haven't we?18:45
AJaegerdhellmann: best talk with StevenK and Daisy how to do this on the Zanata side18:46
dhellmannAJaeger : ack, I'll put it on the summit topic list18:47
dimsnice catch AJaeger18:47
AJaegerdo you have a complete list of projects you create branches for? That might be easier for me to parse than the review list...18:49
dhellmannAJaeger : see the top section of
dhellmannAJaeger : the ones with the "Stable" column filled in have branches18:50
AJaegerdhellmann: thanks18:54
dhellmannsridhar_ram1 : there are an uncomfortable number of requirements changes in those liberty releases. in the future, you're going to want to be careful if you want to actually claim support for the stable process18:57
sdaguedhellmann: I believe so as well, I'm just trying to get a sense because I think we need to wait for requirements before the devstack / grenade branching to be safe19:05
sdagueand that gives us an upgrade testing exposure until that's in play19:05
dhellmannI guess with everything frozen we could technically branch requirements now19:06
* dhellmann resolves to write this down when we figure it out19:06
dhellmannmriedem, ttx: thoughts? ^^19:06
dimsdhellmann : sdague : congressclient is still merging
patchbotdims: patch 293441 - requirements - prevent installing old releases of congressclient19:07
dhellmanndims : oh, thanks19:08
sdaguedhellmann: we also need the projects in the main jobs so swift, keystone, cinder still also need branches19:08
dimsdhellmann : mriedem : i lost track of the upper-constaints for python-troveclient19:08
dimsdhellmann : mriedem :
patchbotdims: patch 292652 - requirements - Update upper-constraints for python-troveclient v2...19:08
dhellmanndims : yeah, we're not releasing 2.2.0 as part of mitaka19:09
sdagueand horizon19:10
mriedemdhellmann: seems right to wait to branch the requirements repo until the server projects have19:10
dhellmannsdague, mriedem, dims, ttx: I'm starting to add steps in order under the RC1 section of
mriedemi guess the point being, leave it open in case of last minute changes that a server project needs for it's rc1 right?19:11
sdaguemriedem: right, the risk is more backporting work basically19:11
sdaguedhellmann: ok, I put the thing under R-219:13
sdagueI am fine if this is a next week thing, right after the requirements unfreeze19:14
sdagueit was just close enough that I figured it was time to poke my head up and allocate a chunk of a day somewhere to do the flips (which should be uneventful), but build in buffer time in case there was any fallout19:15
sdaguefeel free to move that bit around to wherever is appropriate in your list19:16
dhellmannmakes sense, and I like the idea of putting things in the calendar so I've moved the other todo items down19:16
*** sridhar_ram1 has quit IRC19:24
*** kro_sniffles is now known as kro_mnckn_doc19:27
*** daemontool has quit IRC19:28
jokke_dhellmann: around?19:33
dhellmannjokke_ : here19:35
jokke_left a question for you into the Liberty libs release requests19:35
jokke_didn't really get what you are looking for there19:36
dhellmannjokke_ : mriedem has been reviewing liberty releases. frankly, those are not going to be a priority this week19:36
dhellmannwe're dealing with rc1 this week19:36
jokke_dhellmann: was expecting so, that's why they werethere last week like agreed ;)19:37
dhellmannjokke_ : yep. just need the stable team to approve19:38
jokke_dhellmann: just did not know that we're waiting mriedem for it19:38
jokke_dhellmann: so flaper87 wasn't enough19:38
jokke_that's why I was wondering19:39
mriedemjokke_: link?19:39
patchbotjokke_: patch 290774 - releases - Release python-glanceclient 1.1.1 Liberty19:39
patchbotjokke_: patch 290524 - releases - Release glance-store 0.9.2 Liberty19:39
AJaegerdhellmann: I suggest to toggle the +A on , it has not merged for a day...19:40
patchbotAJaeger: patch 290746 - glance_store (stable/mitaka) - Update .gitreview for stable/mitaka19:40
AJaegerdhellmann: wait - it has unfullfilled dependencies ;(19:40
dhellmannAJaeger : does that need a rebase?19:42
dhellmannAJaeger : it should have been the first patch on the new branch19:42
AJaegerdhellmann: I don't understand the message and can't help there, just noticed it and wanted to point it out19:42
dhellmannAJaeger : thanks, I'll try rebasing ti19:42
*** kzaitsev_mb has quit IRC19:50
*** ig0r_ has quit IRC19:55
*** rockyg has joined #openstack-release19:56
mriedemjokke_: +1 on the glanceclient release request19:57
*** rockyg has quit IRC19:57
mriedemjokke_: comment in glance-store
patchbotmriedem: patch 290524 - releases - Release glance-store 0.9.2 Liberty19:57
*** rockyg has joined #openstack-release19:57
openstackgerritSteve Martinelli proposed openstack/releases: release keystone rc1 for mitaka
stevemardims: dhellmann ^20:05
dimsstevemar : stray whitespace20:06
stevemardims: noooo20:06
openstackgerritSteve Martinelli proposed openstack/releases: release keystone rc1 for mitaka
dhellmannstevemar : ack, I'll process that after the check jobs run20:07
dimsdhellmann : what exactly do you run?20:08
dhellmanndims : and then make_stable_branch.sh20:08
dimsah ok20:08
dimsdhellmann : i had added those 2 to the bottom of the page - - just wanted to be sure20:09
stevemardhellmann: thank you kindly sir20:09
dhellmanndims : yep. you know you don't need to specify the yaml filename in that first command, right? the script detects the yaml files updated in the latest commit20:09
dimsdhellmann : yep20:10
*** kzaitsev_mb has joined #openstack-release20:16
*** AJaeger has left #openstack-release20:17
jokke_mriedem: thnx20:21
openstackgerritMerged openstack/releases: release keystone rc1 for mitaka
dhellmannstevemar : processing now, was on a call when that finally merged20:39
dhellmannstevemar : and
*** sridhar_ram has joined #openstack-release20:44
stevemardhellmann: and 2x +2/A for you20:44
dhellmann#success keystone's mitaka release is ready20:48
openstackstatusdhellmann: Added success to Success page20:48
stevemardhellmann: \o/20:48
openstackgerritMerged openstack/releases: Release python-glanceclient 1.1.1 Liberty
*** mattoliverau has quit IRC20:59
*** matt6434 has joined #openstack-release20:59
*** matt6434 is now known as mattoliverau21:00
rockygdhellmann, did I miss the log_wg?  DST is messing me up!21:05
jokke_rockyg: 2205 UTC now21:05
rockygAlso, I'd love to get some input for the roadmap from you on release -- mitaka and beyond.  I know you already put out some mail, but, like to get a little more and some focus21:06
*** doug-fish has quit IRC21:11
*** doug-fish has joined #openstack-release21:12
*** kro_mnckn_doc has quit IRC21:19
sridhar_ramdhellmann: to your earlier point on too many requirements changes in liberty release - point well taken. The liberty 0.2.1 release is an one time anomaly as we hooked up ourselves to pick up requirements automatically after
*** dtantsur|afk has quit IRC21:31
johnsomIs this the right place to request a gerrit permissions fix for a project?21:35
johnsomopenstack/neutron-lbaas-dashboard is missing to permissions for the neutron-release group21:35
*** dtantsur has joined #openstack-release21:37
*** sigmavirus24 is now known as sigmavirus24_awa21:48
*** rockyg has quit IRC21:53
johnsomNevermind, I found it.21:54
*** mriedem has quit IRC21:57
*** sridhar_ram1 has joined #openstack-release22:00
*** sridhar_ram has quit IRC22:01
*** odyssey4me has quit IRC22:09
*** odyssey4me has joined #openstack-release22:09
*** SergeyLukjanov2 has joined #openstack-release22:15
*** SergeyLukjanov has quit IRC22:16
*** SergeyLukjanov2 is now known as SergeyLukjanov22:16
*** dims_ has joined #openstack-release22:16
*** gordc has quit IRC22:18
*** dims has quit IRC22:18
*** sridhar_ram1 has quit IRC22:41
*** doug-fis_ has joined #openstack-release22:47
*** doug-fish has quit IRC22:50
*** doug-fis_ has quit IRC22:51
*** mriedem has joined #openstack-release22:57
*** sridhar_ram has joined #openstack-release23:09
*** krotscheck has joined #openstack-release23:11
*** sdague has quit IRC23:14
*** mriedem1 has joined #openstack-release23:35
*** mriedem has quit IRC23:37
*** doug-fish has joined #openstack-release23:43

Generated by 2.14.0 by Marius Gedminas - find it at!