Monday, 2016-03-28

*** kzaitsev_mb has joined #openstack-release00:37
*** kzaitsev_mb has quit IRC00:42
*** mriedem has quit IRC01:19
*** kzaitsev_mb has joined #openstack-release01:38
*** kzaitsev_mb has quit IRC01:43
*** Qiming has joined #openstack-release01:52
*** kzaitsev_mb has joined #openstack-release02:03
*** sdake has joined #openstack-release02:11
*** sdake has quit IRC02:18
*** kzaitsev_mb has quit IRC02:21
*** mhayden has quit IRC02:43
*** mhayden has joined #openstack-release02:43
*** mhayden has quit IRC02:51
openstackgerritMerged openstack/releases: Final set of Oslo Library Releases for Mitaka  https://review.openstack.org/29772003:06
*** mhayden has joined #openstack-release03:16
*** pcaruana has joined #openstack-release06:49
*** armax has joined #openstack-release08:44
*** armax has quit IRC08:49
*** Qiming has quit IRC09:17
*** Qiming has joined #openstack-release09:17
*** kzaitsev_mb has joined #openstack-release09:31
*** pcaruana has quit IRC09:42
*** vgridnev has joined #openstack-release09:53
*** pcaruana has joined #openstack-release09:55
*** Qiming has quit IRC10:24
*** sdague has joined #openstack-release10:27
*** pcaruana has quit IRC11:09
*** pcaruana has joined #openstack-release11:23
*** doug-fish has joined #openstack-release11:27
*** Qiming has joined #openstack-release11:30
*** gordc has joined #openstack-release11:33
*** vgridnev has quit IRC11:38
dimsttx : dhellmann : one windows bug showed up from last nights oslo.messaging - https://bugs.launchpad.net/oslo.messaging/+bug/1562706 - we have a fix, wondering if we should do a emergency release11:39
openstackLaunchpad bug 1562706 in oslo.messaging "Socket option TCP_USER_TIMEOUT does not exist on Windows" [Undecided,In progress] - Assigned to Davanum Srinivas (DIMS) (dims-v)11:39
dimsttx dhellmann : talking to claudiu, they are covered - http://eavesdrop.openstack.org/irclogs/%23openstack-oslo/%23openstack-oslo.2016-03-28.log.html#t2016-03-28T10:17:48 - so question is do we want to cut a 4.6.1 with that fix for others?11:40
*** flaper87 has quit IRC11:48
*** flaper87 has joined #openstack-release11:51
ttxdims: better before release than after I guess...12:09
ttxbut you may wait for dhellmann for a final call12:09
openstackgerritgordon chung proposed openstack/releases: python-ceilometerclient 2.4.0 - mitaka  https://review.openstack.org/29821212:10
*** vgridnev has joined #openstack-release12:23
dimsttx : ack12:23
ttxprocessing cloudkitty 0.5.012:29
ttxsheeprine: would you have a tag for cloudkitty-dashboard as well ?12:31
AJaegerdhellmann, ttx,dims: Translators are really busy this time. Do you still take translations?12:31
ttxAJaeger: yes12:33
*** amrith is now known as _amrith_12:33
ttxAJaeger: holiday here so I'll skip on processing stable/mitaka12:33
ttxAJaeger: I think dhellmann will12:33
AJaegerttx, enjoy! Thanks12:34
AJaegerdhellmann: list of open translations https://review.openstack.org/#/q/status:open+topic:zanata/translations,n,z12:34
AJaegerdhellmann: translations look fine to import12:35
openstackgerritMerged openstack/releases: Release of CloudKitty 0.5.0  https://review.openstack.org/29793612:37
*** pcaruana has quit IRC12:39
ttxwow bindep on the test nodes ends up installing firefox12:44
ttxprobably some JS testing thing12:48
*** pcaruana has joined #openstack-release12:52
AJaegerttx, yes. We're now ready to move firefox install to those repos that need it.12:54
AJaegerBut it's not high priority so far...12:54
*** mriedem has joined #openstack-release13:35
dhellmannttx, dims : yeah, if you have a fix ready to go let's release oslo.messaging13:45
dimsdhellmann : ack. it's merging now13:45
*** openstackgerrit has quit IRC13:48
*** openstackgerrit has joined #openstack-release13:48
dimsdhellmann : ttx : are we going to "fix" upper-constraints.txt by hand for all the latest libs?13:48
dimsmriedem : ^^13:49
mriedemdims: on stable/mitaka?13:50
dhellmannyes, we need to do that by hand13:51
dhellmannit would be good to have that automated13:53
dhellmannmriedem, AJaeger, ttx: do we usually wait for projects to merge the translations themselves, or should I go ahead and approve those?13:53
mriedemdoes nova have open stable/mitaka translations? /me looks13:54
dhellmannhttps://review.openstack.org/#/q/status:open+branch:stable/mitaka+topic:zanata/translations13:54
AJaegerdhellmann: ttx approved them normally to not wait for the projects13:54
mriedemdhellmann: i don't have +2 on stable/mitaka anyway13:54
mriedembut +1 on https://review.openstack.org/#/c/297538/13:54
patchbotmriedem: patch 297538 - nova (stable/mitaka) - Imported Translations from Zanata13:54
mriedemdhellmann: ttx: also, nova will need https://review.openstack.org/#/c/298068/ in stable/mitaka before we can land any code changes in stable/mitaka13:55
patchbotmriedem: patch 298068 - nova (stable/mitaka) - Update cells blacklist regex for test_server_basic...13:55
*** _amrith_ is now known as amrith13:56
dhellmannmriedem : only the release team for nova has +2 right now (and the release managers), are you not in nova-milestone?13:56
mriedemdhellmann: apparently not13:56
mriedemthis group is super old https://review.openstack.org/#/admin/groups/54,members13:57
mriedemjohnthetubaguy isn't in there, nor is bauwser our release CPL13:57
dhellmannmriedem : you are now, we can clean it up further as part of starting newton13:57
dimsmriedem : yes13:58
dhellmannmriedem :ok, I added both of you13:58
mriedemdhellmann: done, thanks13:58
dimsmriedem : yes on stable/mitaka, the u-c should reflect latest releases13:58
dimsof our own libs13:58
*** sigmavirus24_awa is now known as sigmavirus2413:59
AJaegerdhellmann: ttx and most projects do +2A by single person for translation imports. Remember also, we have every morning this import, so a +2 easily expires14:01
dhellmannok, all the translation patches are approved14:02
AJaegerthanks, ,dh14:02
AJaegerthanks, dhellmann14:03
dhellmanndims : I'm going to process the ironic client releases, unless you're working on a release?14:06
dimsdhellmann : nope, was waiting on the oslo.messaging stuff to merge. please go ahead14:07
*** hongbin has joined #openstack-release14:08
dhellmanndims : thanks, I'll let you know when I'm done so we can pass the lock back and forth14:09
dimssounds good dhellmann14:09
*** doug-fis_ has joined #openstack-release14:19
*** doug-fish has quit IRC14:21
openstackgerritDoug Hellmann proposed openstack/releases: python-ironic-inspector-client 1.6.0  https://review.openstack.org/29745414:31
openstackgerritDoug Hellmann proposed openstack/releases: Cap Sphinx < 1.4 to avoid issue with Babel  https://review.openstack.org/29825914:31
dhellmanndims : new sphinx is breaking our doc build ^^14:31
dimsdhellmann : +2A14:32
dimson the sphinx review14:32
dhellmannthanks, let's see if that fixes it in the gate14:33
*** sdake has joined #openstack-release14:42
*** sdake has quit IRC14:46
*** sdake has joined #openstack-release14:47
openstackgerritDoug Hellmann proposed openstack/releases: Cap Sphinx < 1.4 to avoid issue with Babel  https://review.openstack.org/29825914:54
openstackgerritDoug Hellmann proposed openstack/releases: python-ironic-inspector-client 1.6.0  https://review.openstack.org/29745414:54
dimsdhellmann : so we have network disruptions in rax. possible git corruption cause projects to vanish in gerrit...14:58
dhellmannwow15:02
dhellmannthis may not be a good time to tag releases15:02
dhellmanndims : thanks for the heads-up, I'll follow -infra15:03
*** vgridnev has quit IRC15:17
*** vgridnev has joined #openstack-release15:18
sdakedhellmann we had talked about sorting out liberty kolla tagging today but with ttx's -1, i think I need to fix some things up in the governance repo first15:19
sdakehttps://review.openstack.org/#/c/298278/15:19
patchbotsdake: patch 298278 - governance - Add type:deployment to release:cycle_with_miestones15:19
sdakedhellmann so lets put that liberty change on hold until the governance repo thing is sorted out15:20
dhellmannsdake : yeah, I need to read through your proposal there. My initial reaction, without having read what you wrote, is to say "why not use release:cycle-with-intermediary"?15:21
sdakelet me check thato ne moment15:21
dhellmannthat would encourage you to prepare releases before the end of the cycle, and updates as needed15:21
-openstackstatus- NOTICE: Gerrit is restarting on review.openstack.org in an attempt to address an issue reading an object from the ec2-api repository15:22
dhellmannand it avoids the special case15:22
sdakedhellmann i htink that suffers from the same problem as release:cycle_with_milestones15:22
sdakei dont want releaseindependent or kolla15:23
sdakeit is all i thought we could commit to15:23
sdakebecause we llag the normal release 7-10 days15:23
sdakebecause eveyrone makes last minute deprecations and other annyances15:23
sdakeand some projects are late15:23
sdakekolla most closely matches release_cycle_with_milestones15:24
sdakeminus the fact our final tag lags 7-10 days15:24
sdakedhellmann i'm struggling to understand the difference actully between indermediatary and with milestones15:26
sdakeis with milestones ust mean that we produce an rc1/rc2/rc3/m1/m2/m3 as proposed by the schedule?15:26
dhellmannwell, intermediary produce full releases at any point, not milestones15:26
sdakeya, we produce milestone on the scheudle published15:27
dhellmannthey're subject to the same schedule, though15:27
dhellmannok, yeah, if you're not producing full releases a milestone may make more sense15:27
*** armax has joined #openstack-release15:27
sdakei want us strictly following the ilestones because i want release:managed ;)15:27
sdakeand we do strictly follow the milestones15:27
sdakebut the final release is challenging for us because a) projects re late b) projects change options which break said projects c) interactions of projects sometimes change via default config options15:28
dhellmannok. I'm going to need to think about this some more. It might be simpler to create a new release model instead of building in an exception, but that may also be overkill15:28
sdakeya i had thought of that, but seemed overkill15:29
sdakeand wold trigger changes all over the governance repo :(15:29
dhellmannnone of those things should be happening if projects obey the feature freeze rules15:29
sdakethey hpapen :)15:29
*** Qiming has quit IRC15:29
sdakeeven compute kit projects15:29
sdaketherew was this user-name thing15:29
sdakeintroduced last cycle15:29
dhellmannperhaps you should set up co-gate jobs with some projects to help prevent that15:30
sdakethat caused all kinds of havoc15:30
sdakedhellmann we were thiinking of that15:30
sdakedhellmann its been discussed but our current gate is in such bad shape we want to focus on that for the moment15:30
dhellmannah, yeah, that would be a prereq15:30
sdakewe dont yet have a voting functional gte15:30
sdake(because we don't have mirrors of the software we buid lfrom in infra)15:31
sdakedhellmann well i trust tc can sort it out - the reviews are up for discussion :)15:31
dhellmannyeah, the tc approves those changes but I suspect this is going to get thrown back to the release team to clarify15:32
dhellmanntoday's not a good day for me to stop to think about it, but it's on my list15:32
sdakeya no super rush15:32
sdakei just dont want to be kicked out of the rleases repo foreer15:32
dhellmannoh, you just need to move the file to the _independent directory for now15:32
sdakeits a good way of marketing kolla (is my rationale)15:32
sdakeoh I can do that15:33
sdakethen we can move it back later?15:33
dhellmannnext cycle we're going to try supporting unofficial projects in the repo, too15:33
dhellmannsdake : yeah, if we decide that a cycle-based model makes sense we can move it back15:33
sdakeif i move it to independent and we get clarification on the release:withmilestones, it can be moved bcack?15:33
sdakeok looks like one ofe of us is lagged15:34
sdakethanks dhellmann  :)15:34
sdakedhellmann note kolla is official - in the governance repo15:35
sdakebig tent project15:35
dhellmannsdake : right, I was just making the point that we're trying to be flexible15:35
sdakecool15:35
*** kzaitsev_mb has quit IRC15:39
*** vgridnev has quit IRC15:44
*** vgridnev has joined #openstack-release15:49
dhellmannsdake : do you have a way to get in touch with the magnum team? we haven't heard from them about a release this cycle15:49
*** kzaitsev_mb has joined #openstack-release15:49
sdakei do15:50
sdakei recruited the new ptl originallly - we are good friends15:50
sdakeand worked closely with the old ptl originally15:50
dhellmannok, I have been unable to get anyone to reply to me, so I would appreciate it if you'd ask them to send someone around to chat15:50
sdakeyou got it15:51
dhellmannthanks!15:51
ttxdhellmann: need me for anything ?15:53
dhellmannttx: I don't think so. We had a gerrit issue that meant we stopped tagging for the time being, and then a sphinx issue that prevented us from landing fixes, so I've been updating our status in https://etherpad.openstack.org/p/mitaka-release-tracking15:54
dhellmannI think both issues are resolved, so I'm just waiting for things to merge now15:54
ttxdhellmann: about liberty openstack/releases coverage... After all I'm not sure we should have Ansible or Kolla there, since they missed the liberty release back then (and were clearly release:independent back then)15:55
dhellmannttx: yeah, sdake and I were just talking about that for kolla15:55
ttxI feel like that would only bring confusion to our users as they see new things appearing on that page, which should have a static list of projects frozen from 6 months ago15:56
dhellmannso you'd rather we add those as independent releases? or not show them at all?15:56
ttxThey may regret it now but back then they kinda liked the idea of being able to release one week too late15:56
sdakedidn't like - forced into it :)15:57
sdakettx: https://review.openstack.org/#/c/298278/15:58
patchbotsdake: patch 298278 - governance - Add type:deployment to release:cycle_with_miestones15:58
ttxdhellmann: it's a bit tricky15:58
dhellmannttx: yeah, this keeps coming up so I'd like to figure out some sort of solution15:58
ttxI'm trying to see what would be the less confusing and the most future-proof15:58
ttxdhellmann: the way we decided to handle it this time around was to freeze the release model way before release15:59
sdakettx let me know if this explains the release:indepndent thinking https://review.openstack.org/29830015:59
ttxbut that doesn't prevent some projects from changing at the last minute when they realize they won't appear on the page15:59
dhellmannttx: right, and that was ok for this cycle, but we have all of this history, too15:59
ttxthere are three axis16:00
ttxOfficial / non-official, in the release, not in the release by release time, and document the history16:00
ttxdocument the history + handle stable/liberty releases, I guess16:01
dhellmannyeah16:01
ttxTo handle stable/liberty we said we could have a header in the yaml to use the repo without publishing the entry16:01
dhellmannwe talked about an _unofficial directory under deliverables, maybe we can just make that _other and throw everything in there16:01
dhellmannoh, right, that16:02
dhellmannI forgot about the header, that was the better solution16:02
ttxto document the history I think the yaml in the repo would be enough16:02
ttxwe said we would not list unofficial-by-then things16:02
dhellmannright16:03
ttxbut things that were official but late for release... that's another grey area16:03
ttxmore generally it's the question of how do we handle things that change release model16:03
dhellmannif we set aside the issue of deployment tools, I think if you miss the deadline your release shouldn't be listed16:03
sdakei really hate exceptions16:03
ttxwe should list them as _independent and then move them to per-cycle when they change the model... bu thtat would certainly look funny on the site16:04
sdakebut deployment tools need such a thing as the documents are currently written16:04
*** adrian_otto has joined #openstack-release16:04
dhellmannsdake : yeah, that's why I said setting that question aside -- we need to resolve that separately16:04
ttxsdake: do you think Kolla would be able to stick to the cycle ?16:04
*** vgridnev has quit IRC16:04
ttxor would naturally lag, like Fuel ?16:04
sdakettx we have stuck to the cycle except for mitaka-1 where i was ill with a root canal that failed16:05
sdakefor the final tag, thiis is challenging16:05
ttxsdake: and liberty16:05
sdakeliberty was on tiem for all of our tags iirc16:05
sdakeor 1 or 2 days late16:05
adrian_ottoo/16:05
ttxend release tag was more than one week late16:05
ttxadrian_otto: o/16:05
sdakebut the final relese was late16:05
sdakettx rgiht16:05
sdakedhellmann adrian_otto can help you with magnum release16:05
dhellmannadrian_otto : hi! I'd like to make sure your set for the mitaka release for magnum. I see 2.0.0 was tagged 18 Mar, is that your final?16:06
ttxsdake: maybe we need a special category on the release site for deployment things16:06
sdakethe reason the final release is always late for deployment projects is that binary packaging is 1 week late, projects change things at the last minute which break our integrated softwree16:06
ttxsdake: with special release rules and all16:06
adrian_ottodhellmann: yes sir.16:06
dhellmannadrian_otto : oh, and you have a stable branch set up already, too, so that answers my next question16:06
ttxsdake: yep, we might need to encode that around the type:deployment thing16:07
dhellmannadrian_otto : do you want to list the release on releases.openstack.org?16:07
adrian_ottodo I need to take any action to indicate the release?16:07
sdakettx i submitted a patch to encode type:deployment into release:cycle_with_milestones16:07
ttxIt just might be (way) too late for mitaka, so maybe we should list in _independent for the time being (so that it appears somewhere) while we clean up our act16:07
dhellmannadrian_otto : if you want it listed among the other official projects, you should submit a patch to openstack/releases -- see the readme for details16:07
ttxsdake: ok, I'll have a look at that soon. Today is a holiday around here16:07
sdakettx yup i realize i'm late to figuring out this was a problem :)16:07
adrian_ottodhellmann: ok, will do.16:08
sdakettx got it, well enjoy the holiday :)16:08
dhellmannadrian_otto : thanks16:08
adrian_ottoI will read that when I get to the office.16:09
*** adrian_otto has quit IRC16:09
openstackgerritMerged openstack/releases: Cap Sphinx < 1.4 to avoid issue with Babel  https://review.openstack.org/29825916:11
*** kzaitsev_mb has quit IRC16:12
openstackgerritClaudiu Belu proposed openstack/releases: os-win 0.4.0  https://review.openstack.org/29830316:12
dhellmannyay16:13
ttxdhellmann: weird double announce for cloudkitty16:13
dhellmannttx: hmm16:14
ttxthe email apparently went out twice16:14
dhellmanndifferent content, so the job ran twice16:14
dhellmannthey have both openstack-server-release-jobs and publish-to-pypi16:14
dhellmannif they're a server, they shouldn't have publish-to-pypi16:15
* dhellmann bangs head on wal16:15
dhellmannl16:15
dhellmannsheeprine : ^^16:15
dhellmannttx: we need a bot to look up the liaison for a project by name16:15
jrollfwiw, I'd love to publish servers to pypi :)16:16
dhellmannjroll : one step at a time16:16
openstackgerritMerged openstack/releases: python-ironic-inspector-client 1.6.0  https://review.openstack.org/29745416:16
jrolldhellmann: yep16:16
dhellmannttx, sheeprine : https://review.openstack.org/29830716:19
ttxdhellmann: +116:20
dhellmannbetherly, jroll : did you see my comments on https://review.openstack.org/297386 ?16:23
jrolldhellmann: the one time I didn't check the commit...16:24
jrollor maybe I just derped and overlooked the branch16:24
jrollI can update quickly16:24
dhellmannok16:24
openstackgerritMerged openstack/releases: python-ironicclient 1.3.0  https://review.openstack.org/29745216:24
*** adrian_otto has joined #openstack-release16:24
openstackgerritJim Rollenhagen proposed openstack/releases: Release ironic-ui 1.2.0  https://review.openstack.org/29738616:25
jrolldone, thanks for pointing that out16:25
jrolldhellmann: when you have time, want to chat about https://review.openstack.org/#/c/295966/ ?16:27
patchbotjroll: patch 295966 - releases - ironic 4.2.316:27
dhellmannjroll : our general policy is to not change lower bounds on dependencies for stable branches, esp. not for bugs. In this case, a change to exclude the requirement would be ok but only if we need that in our own gate. a release note about compatibility with dependencies should be good enough for downstream consumers, especially if we indicate through the constraints file what version we're testing with.16:29
openstackgerritMerged openstack/releases: Release os-brick 1.2.0  https://review.openstack.org/29737116:29
*** cody-somerville has quit IRC16:31
*** cody-somerville has joined #openstack-release16:31
*** cody-somerville has joined #openstack-release16:31
jrolldhellmann: so "ironic fails to start up when scciclient 0.2.0 is installed in the system" is not a valid reason to update an optional requirements list that packagers look at?16:32
dhellmannjroll : you can exclude that version, but not raise the minimum16:32
dhellmannwhat was the minimum before?16:33
jrolldhellmann: 0.2.0 was the minimum before16:33
*** armax has quit IRC16:33
dhellmannbah16:33
jroll0.3.0 was the next release16:33
dhellmannok, so we don't want to change stable requirements at all, really16:33
dhellmannthis is an optional thing? and you can't work around in your code whatever causes it to fail to start?16:34
dhellmannmriedem : thoughts on ^^?16:34
jrollnope, installing it installs pbr<1.0, which breaks ironic startup somehow16:34
dhellmannah16:34
dhellmannthat makes me more likely to approve the change16:34
dhellmanntonyb : thoughts? ^^16:35
jrollthe other library update isn't so nasty, it just starts failing all over the place after running for a while16:35
jrollso I guess that could be reverted16:35
dhellmannlet me get mriedem or tonyb to chime in, but I'll remove my -116:36
jrollthey've both commented already, fwiw16:37
jrollbut yeah will wait16:37
mriedemjroll: dhellmann: so this https://review.openstack.org/#/c/253362/2/driver-requirements.txt16:39
patchbotmriedem: patch 253362 - ironic (stable/liberty) - Update python-scciclient version number (MERGED)16:39
jrollmhm?16:40
mriedemso python-scciclient 0.2.0 installs pbr<1.016:40
mriedemi'm catching up16:40
mriedempbr<1.0 was a kilo thing16:40
jrollyes16:40
mriedemso basically, ironic on liberty was using kilo-level dependencies and their caps16:41
jrollthat repo did not have requirements sync set up at that time16:41
jrollironic *with that optional dependency*, yes16:41
mriedemwell, does it even sync to driver-requirements.txt? those are optional16:41
jrollthat dep is completely optional for a driver16:41
jrollright, the scciclient repo did not have syncing16:41
jrollnothing syncs driver-reqs16:41
dimsdhellmann : am back on16:42
jrollthose are not necessarily in g-r16:42
jrollnor are they part of an official project team16:42
mriedemyeah python-scciclient isn't even in global-requirements16:43
mriedemhmm it is in openstack though https://github.com/openstack/python-scciclient16:43
mriedemshould probably be in g-r16:43
mriedemhowever, it wouldn't help here anyway since it's not in requirements.txt16:44
*** david-lyle_ has joined #openstack-release16:44
jrollright, and driver-reqs was updated as soon as that was released16:44
jrollit was only released to fix this issue16:44
*** david-lyle has quit IRC16:44
mriedemok, i was thinking if we could fix scciclient and release a 0.2.1, but that doesn't really work, since that could break ironic on kilo (for this dependency)16:45
mriedemso really, this is just a thing that ironic should have updated the minimum version of prior to the liberty GA16:45
mriedemsince it's optional no one tested until it was too late, i guess16:45
mriedemi don't really see a way around this16:46
jrollit wasn't found until mitaka, yeah16:46
jrollditto for the other16:46
*** david-lyle has joined #openstack-release16:48
*** armax has joined #openstack-release16:48
*** david-lyle_ has quit IRC16:49
dhellmannmriedem : I agree. Do you want to document that in a comment on the release patch, and then I'll process it after lunch?16:49
dhellmannassuming zuul eventually catches up with the release I just approved, that is :-)16:50
mriedemdhellmann: sure16:51
openstackgerritAdrian Otto proposed openstack/releases: magnum 2.0.0 - mitaka  https://review.openstack.org/29832416:55
openstackgerritAdrian Otto proposed openstack/releases: python-magnumclient 2.0.0 - mitaka  https://review.openstack.org/29832716:58
adrian_ottodid I do the Depends-On correctly in https://review.openstack.org/298327 ?17:00
adrian_ottoor should that have been a commit hash as the argument?17:00
dhellmannadrian_otto : looking17:01
dhellmannadrian_otto : it should be the Change-Id value from the commit message of the patch17:01
adrian_ottook, I'll fix that, thanks dhellmann17:01
dimsadrian_otto : just registering the release already made right?17:02
dhellmannadrian_otto : and if that's the requirement patch, you want the dependency to go the other way17:02
adrian_ottooh, ok17:03
dhellmannadrian_otto : oh, yeah, we can't change the requirements in that way right now17:03
dhellmannrequirements freeze was a couple of weeks back :-/17:03
adrian_ottoso what should we do?17:03
openstackgerritAdrian Otto proposed openstack/releases: python-magnumclient 2.0.0 - mitaka  https://review.openstack.org/29832717:04
adrian_ottoI just pulled out the Depends-On then.17:04
dhellmannadrian_otto : I have a call shortly, then I'll look at your changes17:04
*** vgridnev has joined #openstack-release17:07
dimsadrian_otto : just registering the releases already made right?17:07
*** themarcelor has joined #openstack-release17:07
adrian_ottoyes.17:07
adrian_otto^^ dims17:08
*** themarcelor has left #openstack-release17:08
dimsadrian_otto : the references to python-magnumclient looks good - http://codesearch.openstack.org/?q=%5Epython-magnumclient&i=nope&files=&repos=17:08
dimsadrian_otto : except for upper-constraints.txt17:08
dimsdhellmann : ^^17:09
adrian_ottodims: see https://review.openstack.org/29681017:11
adrian_ottowhat am I missing?17:11
dhellmannadrian_otto : there are a couple of issues. first, we've already branched the requirements for mitaka, so you need to make changes to both master and stable/mitaka in the requirements repository17:21
dhellmannadrian_otto : second, we can't raise the minimum version of the library in stable/mitaka17:21
dhellmannwhen we do unfreeze the requirements repo in master, we can change the minimum there17:22
adrian_ottook, but 1.x clients can not use magnum 2.x17:22
adrian_ottoso all three of my patches should just be repeated for stable/mitaka17:23
adrian_ottoand you can decide when to merge them17:23
dhellmannadrian_otto : the old version of the client is not compatible with the new version of magnum?17:24
*** david-lyle has quit IRC17:24
*** david-lyle has joined #openstack-release17:25
adrian_ottodhellmann: yes.17:26
dhellmannthat's unfortunate17:26
adrian_ottoagreed17:26
adrian_ottothat's why API versioning is in the plan for Newton17:27
dhellmannyeah17:27
dhellmannthe feature freeze and client release freeze was back around march 3. so far, we've rejected other projects updating minimum requirements for mitaka if they've missed that deadline. we'll have to look at which changes we can approve going forward17:28
*** dtantsur is now known as dtantsur|afk17:39
jrolladrian_otto: does anything depend on the magnum client?17:40
jrollany code, I should say17:41
dimsjroll : heat/murano - http://codesearch.openstack.org/?q=%5Epython-magnumclient&i=nope&files=&repos=17:41
dimsat least it's in their requirements17:41
jrolldang :(17:41
*** doug-fis_ has quit IRC17:43
adrian_ottojroll: yes, that's new17:45
*** kzaitsev_mb has joined #openstack-release17:47
openstackgerritClaudiu Belu proposed openstack/releases: os-win 0.4.0  https://review.openstack.org/29830318:00
*** doug-fish has joined #openstack-release18:04
*** doug-fis_ has joined #openstack-release18:05
*** vgridnev has quit IRC18:06
*** doug-fish has quit IRC18:09
*** david-lyle_ has joined #openstack-release18:12
*** david-lyle has quit IRC18:14
*** pcaruana has quit IRC18:16
*** flwang has quit IRC18:21
openstackgerritCraig Vyvial proposed openstack/releases: trove-dashboard release 6.0.0.0rc2  https://review.openstack.org/29836518:26
*** cp16net has joined #openstack-release18:26
openstackgerritMerged openstack/releases: python-ceilometerclient 2.4.0 - mitaka  https://review.openstack.org/29821218:28
*** pcaruana has joined #openstack-release18:30
*** vgridnev has joined #openstack-release18:33
*** sdake_ has joined #openstack-release18:34
*** sdake_ has quit IRC18:35
*** hongbin has quit IRC18:36
*** hongbin has joined #openstack-release18:36
*** sdake has quit IRC18:37
*** sdake has joined #openstack-release18:39
*** doug-fis_ has quit IRC18:43
*** doug-fish has joined #openstack-release18:44
*** sdake has quit IRC18:44
*** sdake has joined #openstack-release18:48
openstackgerritBen Swartzlander proposed openstack/releases: Release Manila UI 2.1  https://review.openstack.org/29837718:56
dhellmanndims : were you going to update the constraints for the mitaka oslo libs? I'm going to do some of the others.18:58
dimsdhellmann : yes, i'll file reviews in master and stable/mitaka in upper-constraints.txt for all oslo libs18:59
dhellmanndims : hmm, I was only doing stable/mitaka for now18:59
dhellmannwe would want a newer master release before updating master19:00
dimsdhellmann : all changes in stable/mitaka are already on master, so it should be ok. right?19:01
dhellmanndims : it should be, but it feels weird to insert stable branch releases into master19:01
dimsi see what you are saying19:01
dhellmannif we already had a newer master release, we wouldn't do it19:02
dimsright19:02
openstackgerritDavanum Srinivas (dims) proposed openstack/releases: Release for oslo.messaging 4.6.1 to fix Windows CI failure  https://review.openstack.org/29838319:11
dhellmanndims : I have a script ready to update all of the constraints at once, so don't spend a bunch of time on that19:13
dhellmanndims : "that thing where you sit down to write a tool and found you've already done it"19:13
dimsdhellmann : i just filed it https://review.openstack.org/#/c/298384/19:14
patchbotdims: patch 298384 - requirements (stable/mitaka) - Final Oslo releases for Mitaka19:14
dimsdhellmann : LOL19:14
dhellmanndims : ok19:14
dimsdhellmann : need an intelligent editor to say "Didn't you just do this last week?" :)19:14
dhellmanndims : seriously19:15
dhellmanneither that or I need to start looking before I sit down to write a script :-)19:15
dims:)19:16
dhellmanndims : let's see if we get the same answers :-)19:16
dimsthe game is on!19:16
dims:)19:16
*** doug-fis_ has joined #openstack-release19:22
*** doug-fish has quit IRC19:25
*** doug-fis_ has quit IRC19:27
*** doug-fish has joined #openstack-release19:28
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: improve check_library_constraints.sh to edit the constraints file  https://review.openstack.org/29839819:33
*** sdake_ has joined #openstack-release19:36
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: improve check_library_constraints.sh to edit the constraints file  https://review.openstack.org/29839819:37
*** sdake has quit IRC19:38
openstackgerritDavanum Srinivas (dims) proposed openstack/releases: Release for oslo.messaging 4.6.1 to fix Windows CI failure  https://review.openstack.org/29838319:52
dhellmanndims : https://review.openstack.org/29840919:52
dimsdhellmann : looks good.19:55
dimsdhellmann : i abandoned mine.19:55
dhellmanndims : also https://review.openstack.org/29839819:55
dhellmannoh, I was going to compare the results :-)19:55
dhellmannI should have rebased mine on yours and resolved the conflicts19:56
dimsdhellmann : i did compare the results, only thing was 4.6.1 which we are yet to cut https://review.openstack.org/#/c/298383/19:56
patchbotdims: patch 298383 - releases - Release for oslo.messaging 4.6.1 to fix Windows CI...19:56
dhellmanndims : oh, is that why yours was failing the jobs?19:56
dimsy19:56
dimsi had a Depends-On19:56
dimsso, we should get yours in, so we can check CI output without waiting for 4.6.119:57
dimsand then we can throw in 4.6.1 later today or early tomorrow AM19:57
dhellmannsounds good19:57
dimsmriedem : want to peek at https://review.openstack.org/#/c/298409/ ?19:58
patchbotdims: patch 298409 - requirements (stable/mitaka) - update mitaka constraints for most recent lib rele...19:58
dimsdhellmann : if i don't heat from mriedem in an hour, i'll +2A and watch CI19:59
dimss/heat/hear/19:59
*** sdake has joined #openstack-release20:03
mriedemdims: dhellmann: so what's the idea here?20:03
mriedemthese are newton versions of libs? or mitaka?20:04
mriedemassuming mitaka since we aren't releasing new things for newton yet?20:04
dhellmannmriedem : these are all mitaka, released from stable branches to update the requirements settings in those libs20:04
mriedemoh, per the ML thread about this last week...20:05
mriedemwhen stable/mitaka g-r sync went out20:05
mriedemright?20:05
*** sdake_ has quit IRC20:06
mriedemwhat happened with neutron-lib version going down?20:06
dhellmannmriedem : 0.2.0 is part of newton, and isn't on the stable branch20:07
dhellmannmriedem : I used https://review.openstack.org/298398 to build that patch20:07
dhellmannarmax, mestery : should I set the constraint for neutron-lib in mitaka to 0.1.0 or 0.2.0?20:09
mriedemseems it should be 0.0.2 given https://github.com/openstack/releases/blob/master/deliverables/mitaka/neutron-lib.yaml#L920:09
*** kzaitsev_mb has quit IRC20:09
dimsdhellmann : may i borrow the release baton to get 4.6.1 of oslo.messaging out? https://review.openstack.org/#/c/298383/20:10
patchbotdims: patch 298383 - releases - Release for oslo.messaging 4.6.1 to fix Windows CI...20:10
dhellmanndims : go for it20:11
dhellmannmriedem : yeah, I pulled this info from the tags on the repo, but with that version number they can't do any releases from that branch anyway20:11
dimsack20:11
dhellmannlet me update the patch20:11
mriedemhmmm, neutron-lib is really painting itself into a corner with those versions20:14
openstackgerritMerged openstack/releases: Release for oslo.messaging 4.6.1 to fix Windows CI failure  https://review.openstack.org/29838320:15
dhellmannmriedem : yeah, we'll address that this cycle20:17
dhellmanndims : oops, are you done? I just approved the os-win release request, too20:23
dimspypi upload just finished dhellmann. so am done20:23
dhellmannwhew20:23
dimsdhellmann : we can fix up your review with 4.6.1 too20:24
dhellmanndims : that'll probably save time in the long run20:24
*** vgridnev has quit IRC20:25
dhellmanndims : I'll hold the update until the releases are done20:25
openstackgerritMerged openstack/releases: os-win 0.4.0  https://review.openstack.org/29830320:28
*** vgridnev has joined #openstack-release20:29
*** vgridnev has quit IRC20:29
*** adrian_otto has quit IRC20:31
dhellmanndims : https://review.openstack.org/298409 is updated20:38
*** flwang has joined #openstack-release20:39
*** sdake_ has joined #openstack-release20:43
*** sdake has quit IRC20:43
*** flwang has quit IRC20:46
*** vgridnev has joined #openstack-release20:49
*** kzaitsev_mb has joined #openstack-release20:50
*** kzaitsev_mb has quit IRC20:55
*** rockyg has joined #openstack-release21:05
*** kzaitsev_mb has joined #openstack-release21:08
tonybdhellmann: anychance you can look at https://review.openstack.org/#/c/294398/ (it passes tests now)21:08
patchbottonyb: patch 294398 - requirements (stable/liberty) - Revert "Tolerate both new and old setuptools"21:08
dhellmanntonyb : so we're reverting a bug fix?21:09
tonybdhellmann: basically yeah21:09
dhellmannwhy bother?21:09
dhellmannI mean, it's fine, I'm just curious21:09
tonybdhellmann: because we added a fix to work around an API changin setuptools that got reverted, now we break.21:10
dhellmannoh, the fix breaks now21:10
dhellmannok, approved21:10
tonybdhellmann: without that "fix" I *think* requirements ar broken on liberty21:10
tonybdhellmann: thanks21:11
dhellmanndims : I'm ready to handle manila-ui if you're done21:11
dimsdhellmann : +121:12
openstackgerritMerged openstack/releases: Release Manila UI 2.1  https://review.openstack.org/29837721:15
*** prometheanfire has quit IRC21:21
*** prometheanfire has joined #openstack-release21:22
*** sridhar_ram1 has joined #openstack-release21:24
*** sdake_ is now known as sdake21:27
sridhar_ram1ttx21:29
*** sridhar_ram1 is now known as sridhar_ram21:29
* sridhar_ram oops21:29
smcginnisAre we still trying to get final releases out by today?21:29
smcginnisIf so, and we also want requirements updates according to the ML, I need this through before I can get it in Cinder and do a final release:21:30
smcginnishttps://review.openstack.org/29737121:30
dhellmannsmcginnis : I processed that one already21:32
smcginnisdhellmann: Oh, sorry, the update one: https://review.openstack.org/#/c/297373/21:32
patchbotsmcginnis: patch 297373 - requirements - Raise upper-constraint and GR for os-brick 1.1.121:32
dhellmannsmcginnis : that updates master, and we don't want to do that. I have a patch to update stable, hang on21:33
dhellmannsmcginnis : https://review.openstack.org/#/c/298409/21:33
patchbotdhellmann: patch 298409 - requirements (stable/mitaka) - update mitaka constraints for most recent lib rele...21:33
smcginnisdhellmann: Ah, thanks!21:33
dhellmannsmcginnis : we'll want a master release when we open newton if you need to raise the minimum requirements21:34
dhellmannsmcginnis : as things are now, we can change the constraints but not the mins in stable/mitaka21:34
dhellmanndims : I'm going to call it a day. We can approve that constraints update first thing tomorrow.21:35
sridhar_ramttx: dhellmann: Hi .. quick update on tacker release.. we are landing last set of patchsets. My hope is to get most of them land by this Thursday. It is going to be tight but the team is working hard to make it. Is there anything I need to be aware of before requesting the release ? Is there any release checklist of sort to go thru' ?21:35
smcginnisdhellmann: OK makes sense. Thanks!21:35
*** doug-fish has quit IRC21:36
smcginnisdhellmann, dims: So final RC cut is okk tomorrow?21:36
dhellmannsmcginnis : yes21:36
smcginnisGood, back to vacation. ;)21:37
dhellmannsridhar_ram : if some of the patches aren't written yet, you should seriously consider putting those features in your newton release. Anything after Thursday will be part of Newton, not Mitaka.21:37
*** yilberivansalced has joined #openstack-release21:38
sridhar_ramdhellmann: these are patchsets in final leg of review.. most of them will land today / tomorrow. Will yank the rest towards Newton release21:39
dhellmannsridhar_ram : sounds good21:39
*** yilberivansalced has left #openstack-release21:40
*** yilberivansalced has joined #openstack-release21:40
*** yilberivansalced has left #openstack-release21:40
*** yilberivansalced has joined #openstack-release21:41
*** yilberivansalced has left #openstack-release21:41
dimsdhellmann : ack, i'll do it first thing when i get online21:43
*** adrian_otto has joined #openstack-release21:51
*** adrian_otto has quit IRC21:54
*** mriedem has quit IRC21:55
*** yilberivansalced has joined #openstack-release21:56
*** yilberivansalced has left #openstack-release21:56
*** adrian_otto has joined #openstack-release21:57
*** doug-fish has joined #openstack-release21:57
*** kzaitsev_mb has quit IRC22:20
*** amrith is now known as _amrith_22:21
*** rockyg has quit IRC22:29
armaxdhellmann: yes, 0.2.022:32
armax0.0.222:32
*** doug-fish has quit IRC22:37
*** gordc has quit IRC22:43
*** sdague has quit IRC22:53
dhellmannarmax : your next release will need to be 0.1.0 in order to get that library onto valid semver versions22:56
openstackgerritgordon chung proposed openstack/releases: ceilometer 6.0.0.0rc2  https://review.openstack.org/29845922:56
*** david-lyle_ is now known as david-lyle22:57
armaxdhellmann: ack22:59
armaxdougwig: ^22:59
openstackgerritgordon chung proposed openstack/releases: ceilometer 6.0.0.0rc2  https://review.openstack.org/29845923:00
dhellmannbetherly , jroll : see the comments on the ironic-ui release https://review.openstack.org/#/c/297386/23:00
patchbotdhellmann: patch 297386 - releases - Release ironic-ui 1.2.023:00
dhellmannadrian_otto : it looks like you grabbed the wrong sha values for https://review.openstack.org/#/c/29832723:04
dhellmannand https://review.openstack.org/#/c/298324/23:04
patchbotdhellmann: patch 298324 - releases - magnum 2.0.0 - mitaka23:04
adrian_ottodhellmann: ?23:05
openstackgerritJim Rollenhagen proposed openstack/releases: Release ironic-ui 1.1.1  https://review.openstack.org/29738623:05
jrolldhellmann: thanks for the poke23:05
jrollupdated commit message too23:05
dhellmannadrian_otto : the validation job does not agree with the shas you've put in that patch, it's finding the tags on different commits23:05
dhellmannadrian_otto : see the log output from the validate job23:06
adrian_ottook23:06
*** vgridnev has quit IRC23:07
*** mriedem has joined #openstack-release23:08
*** kzaitsev_mb has joined #openstack-release23:17
*** kzaitsev_mb has quit IRC23:22
dougwigdhellmann, armax: ack.23:29
*** Qiming has joined #openstack-release23:29
openstackgerritAdrian Otto proposed openstack/releases: magnum 2.0.0 - mitaka  https://review.openstack.org/29832423:37
openstackgerritAdrian Otto proposed openstack/releases: python-magnumclient 2.0.0 - mitaka  https://review.openstack.org/29832723:39
adrian_ottookay, I think that should do the trick, dhellmann. Please let me know if I need any more tweaking to get this right.23:40
dhellmannadrian_otto : ok, that looks good for the server. We should talk about changing your client release model to cycle-with-intermediary for newton. For mitaka, we can move the deliverable file into the _independent directory to record the release, since as an independent project it technically isn't part of mitaka.23:53
*** hongbin has quit IRC23:56
adrian_ottohongbin will be responsible for the changes in the Newton release, as the newly elected PTL23:56
adrian_ottoI can revise the 298327 patch23:57
*** sigmavirus24 is now known as sigmavirus24_awa23:58
openstackgerritMerged openstack/releases: magnum 2.0.0 - mitaka  https://review.openstack.org/29832423:59

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