Thursday, 2016-03-24

*** sdake has quit IRC00:41
*** sdake has joined #openstack-release01:57
*** mtreinish has quit IRC01:59
*** mtreinish has joined #openstack-release02:01
*** mriedem has quit IRC02:11
*** mriedem has joined #openstack-release02:11
*** mriedem has quit IRC03:17
*** sdake_ has joined #openstack-release03:21
*** sdake has quit IRC03:22
*** bswartz has quit IRC03:55
*** bswartz has joined #openstack-release03:56
prometheanfireI've noticed that projects have stable/mitaka branches now, requirements only gets that when the release date is hit?04:26
*** sdake_ is now known as sdake04:29
*** sdake has quit IRC05:16
*** sdake has joined #openstack-release05:18
*** sdake_ has joined #openstack-release05:21
*** sdake has quit IRC05:23
*** sdake_ is now known as sdake05:45
*** pcaruana has quit IRC05:48
*** bdemers has quit IRC06:03
*** bdemers has joined #openstack-release06:07
*** lifeless has quit IRC07:06
*** pcaruana has joined #openstack-release07:32
*** daemontool has joined #openstack-release07:33
ttxprometheanfire: no, we should cut the requirements branch today07:44
ttxdhellmann: ^ I think today is better than tomorrow for that07:44
*** sdake has quit IRC08:02
*** sdake has joined #openstack-release08:06
*** sdake has quit IRC08:18
*** kzaitsev_mb has joined #openstack-release09:02
*** vgridnev has joined #openstack-release09:05
openstackgerritMerged openstack/releases: Release ironic-ui 1.1.0
*** kzaitsev_mb has quit IRC09:27
*** sdague has joined #openstack-release10:24
*** sheeprine has quit IRC10:28
*** sheeprine has joined #openstack-release10:30
openstackgerritSylvain Bauza proposed openstack/releases: Tag Nova Mitaka RC2
*** daemontool has quit IRC10:46
*** lifeless has joined #openstack-release11:07
odyssey4mehmm, something odd has happened - OpenStack-Ansible has disappeared from the releases page11:24
odyssey4meok, found where it is in the repo - it's been moved:
odyssey4mefair enough, but now where does it get published?11:26
odyssey4meah, found it
dimsodyssey4me : cool you found it11:28
odyssey4me:) yeah, thanks11:28
*** _amrith_ is now known as amrith11:30
*** vgridnev has quit IRC11:36
*** vgridnev has joined #openstack-release11:37
*** daemontool has joined #openstack-release12:07
*** TravT has quit IRC12:09
*** daemontool has quit IRC12:15
*** mriedem has joined #openstack-release12:21
*** gordc has joined #openstack-release12:34
*** amrith is now known as _amrith_12:52
dhellmannttx: yeah, we should go ahead and create the stable branch13:11
dhellmannttx: should we tag too? I only see *-eol tags13:12
ttxno tag that I know of13:40
ttxdhellmann: ^13:40
ttxplease branch13:41
* ttx has a look at the mitaka jobs13:41
dhellmannok, branching requirements now13:43
dimsdhellmann : sdague and i have created stable/mitaka branches for devstack and grenade, added info to the etherpad13:44
ttxcan't spot any utter failure on the stable-mitaka jobs that have supposedly run this morning13:44
ttxbut then I have trouble finding them on the multiple-jenkinses13:44
dhellmannok, stable/mitaka is created in the requirements repo and the gitreview update is in CI13:45
dimsdhellmann : ooh and devstack-gate is branchless13:45
dhellmannttx, dims: I'm going through the TODO list items in R-2 to mark anything we've done as completed13:47
dimsdhellmann : ack, just took care of " QA Team to branch devstack / grenade for upgrade / gate testing"13:47
dhellmannare we ready to unfreeze requirements?13:48
dimsdhellmann : i'd give it another day, need to check grenade mitaka jobs are good.13:49
dimssdague : ^^13:50
ttxwe usually do one day of observation13:50
dhellmannsounds good13:50
ttxusually after a few hours sdague comes and tells us the universe just broke13:50
ttxcurious if we got it right this time13:50
dimsdhellmann : whoa the bot already proposed patches
sdagueso, right now, things are looking pretty good13:51
dhellmanna bunch of whitespace changes?13:51
sdaguethere was only 1 grenade bug that I needed to fix before the branch upgrades worked13:51
dimsmriedem : how do you want to deal with bot proposed updates to stable/ branches? (note we have not unfrozen requirements yet)13:52
ttxdhellmann: more than whitespace13:52
dhellmannah, the first one I clicked on was13:52
*** daemontool has joined #openstack-release13:52
dhellmannare these all for projects that never merged their updates in the first place?13:52
ttxwhy does the bot spot a difference ? Should be the same as master/master difference, no ?13:52
ttxswift does not merge updates, but that shall be the only "different" project13:53
mriedemdims: like requirements updates?13:53
mriedemfor stable/mitaka?13:53
dimsmriedem :
ttxdhellmann: I thought we merged all requirements updates while in freeze13:53
dimsmriedem : y13:53
ttxmaybe we missed that step13:53
dhellmannttx: perhaps not?13:53
ttxdhellmann: sad, since that is why we actually freeze13:54
mriedemdims: i'd say just do it the same as always13:54
dhellmannI wonder if there's some way to add that to the validation? if the list-changes job produced a list of unmerged requirements updates on the branch, for example13:54
dimsmriedem : ack just making sure13:55
ttxdhellmann: all libs for some reason13:55
dimsdhellmann : neutron too (not just libs)13:55
ttx+ neutron yes13:56
dhellmannalright, well, now what?13:56
dhellmannshould we merge these?13:56
dimsmriedem : another question : do you want to switch off bot proposing new library versions to openstack/requirements in stable/mitaka13:56
dhellmanncut stable releases?13:56
dhellmanndims , mriedem : we want the automatic constraints updates turned off, but I think those only run in master already?13:57
dimsdhellmann : i'll check13:57
ttxdhellmann: i'd like to understand why we are here first... Are those all (except neutron) libraries that did not have their requirements updates merges over the last 2 months ?13:58
ttxor at least not since lib freeze13:58
dimsdhellmann : teams should evaluate these and propose releases if they really think they need it?13:58
dimsttx : oslo ones...since lib freeze13:58
ttxI'd say we need to cut them13:58
dhellmanndims : I would like to avoid the limbo situation we had with liberty requirements where no one felt comfortable approving13:58
ttxso that we are in a clean state13:59
dimsdhellmann : right13:59
dhellmannlet's get them all cleaned up -- right13:59
dimsdhellmann : so we propose releases by ourselves?13:59
dhellmanndims : we'll need to coordinate with the lib owners, but yeah, something like that14:00
dimsdhellmann : problem is some teams have already backported stuff (oslo.messaging)14:00
dhellmannthat's ok, they did that intending to release it, right?14:00
dimsso it's not just requirements changes14:00
ttxi think that's ok14:00
dhellmannit's still only going to get a patch version update14:00
ttxthink of it as last mitaka release for libs14:01
dimsso we should tell people to review at least14:01
dims+1 ttx14:01
dhellmannthe oslotest change represents a change that was merged in master after stable/mitaka was created14:02
dhellmannthe patch date for that was feb 2614:02
dhellmannso that at least, I think, is one where we cut a stable branch in the lib before we had merged the requirements updates?14:03
dhellmannI wonder if I shouldn't have used openstack/requirements head for the branch.14:03
ttxwe should basically freeze requirements before we cut the branch for libs, and not cut the branch for libs until we have synced the reqs14:03
dimsdhellmann : that's the only option14:03
ttxmight be difficult with the earlier deadlines14:04
dhellmannwe've had several updates to requirements in the last 2 weeks14:04
dimsttx : won't work because libs tend to break which we fix by changing requirements14:04
dhellmannall of those look legit, though14:05
dimsright dhellmann14:05
ttxright, so those should be merged14:05
ttxNone of those releases should trigger a requirement change, right14:06
dimsright, unless something breaks the world14:06
dhellmannttx: they need the constraints file updated14:06
dhellmannand right, what dims said14:06
ttxoh well, maybe that's an artifact of the process then14:07
ttxdidn't expect so many14:07
prometheanfirettx: thanks, I might cut the live ebuild for keystone today as well14:07
ttxlet's try to communicate to PTLs and release as much today as we can, because Friday14:07
ttxalthough I guess we have all week next week too14:07
*** _amrith_ is now known as amrith14:07
ttxdhellmann: maybe mark the ones that shall be updated on the spreadsheet14:08
dhellmannyeah, I'll start recording that14:08
dhellmannan easier list to review:
*** sigmavirus24_awa is now known as sigmavirus2414:09
dhellmannttx, dims, mestery, armax : there's already a neutron-lib 0.0.2 and we have requirements updates for stable/mitaka. I suppose we'll never release a stable update for that lib?14:15
dimsdhellmann : armax : ttx : +1 to merge bot proposed update and re-propose the release with a new SHA14:16
mesterydhellmann: I think you're correct14:16
dhellmanndims : re-propose 0.0.2? we don't have a way to do that14:17
dhellmanndims , ttx: I've added "stable req update" as a special note in the dashboard for the projects that have them14:18
ttxdhellmann: we could also unbranch stable/mitaka there14:18
ttxdhellmann: I don't think anything uses neutron-lib yet ?14:18
dimsdhellmann : ah i thought it was in review14:18
ttxi.e. consider 0.0.1 and 0.0.2 part on Newton14:18
dhellmannmestery , armax : ^^?14:18
ttxa 0.0.1 in stable with a 0.0.2 next is a dead tree anyway14:19
ttxso unless we REALLY need a 0.0.1 in stable/mitaka for some reason...14:19
mesterydhellmann: I'd like to make sure we pull dougwig into this discussion before we decide here. I think what you're saying makes sense, but I'd be more comfortable getting dougwig to +1 as well.14:19
ttxwe already have a number of libs that won't have a mitaka release so there is precedent14:20
ttx(new libs that are not ready and not used)14:20
dhellmannttx: do you have +2 on keystoneauth stable/mitaka?14:21
ttxI suspect not,; checking14:21
stevemardhellmann: need something?14:21
ttxconfirmed no14:21
stevemardhellmann: this patch?
patchbotstevemar: patch 297123 - keystoneauth (stable/mitaka) - Updated from global requirements14:22
dhellmannttx: ok, I'll work on a project-config patch for that14:22
dhellmannstevemar : yeah, your acls on keystoneauth are wrong14:22
stevemardhellmann: should i include a group?14:23
dhellmannstevemar : your stable branch should be locked down right now:
dhellmannttx: ^^14:24
ttxlooking up acl14:24
dhellmannI copied those settings from keystonemiddleware14:25
ttxdhellmann: lgtm14:26
ttxwow that ironic-ui announce email looks completely wrong14:28
ttxdhellmann: seen that ?14:28
*** sdake has joined #openstack-release14:37
dhellmannugh, what is that?14:38
bknudsonare we going to need releases for keystoneauth?14:38
dhellmannbknudson : yes14:38
bknudsondhellmann: minor or major version increase?14:38
dhellmannbknudson : tbd14:38
bknudsonminor or patch I should have said.14:38
dhellmannttx: that come out of the job? it looks like maybe?14:39
dimsouch on the email!14:39
dhellmannttx: or was that the one we did by hand yesterday because the job wasn't there?14:40
dhellmannI don't see an announce job in
ttxdhellmann: no, job output14:40
ttxsent by no-reply and all14:40
ttxwould be good to reply to it with the correct version14:41
dimsdhellmann "{{ description }}" went bad
dhellmannoh, I'm looking at the wrong repo14:41
ttxToday is a bit crazy for me + my wife is sick so I have to use every extra second to care for the kids14:41
dhellmannok, I'll look into this14:42
dhellmannttx: before you step away, I was going to compose email about the stable requirements updates, I'd like you to review it before I send14:42
ttxjust ping me when ready14:42
ttxI'm not really stepping away, just avoiding everything I can14:43
dimsttx : ouch, yes, i am around to help14:43
ttxevasion maneuvers14:43
dhellmannttx, dims:
dimsdhellmann : do we tell them to file reviews with version # and SHA?14:52
dimsor do we do it for them?14:52
dimsthat bit was not clear14:52
dhellmanndims : yeah, I should be more explicit about that14:52
dimsyes please14:52
dhellmannmriedem, dims, ttx: last time we did requirements updates in a stable branch we used patch versions. Should we do that here, or go ahead with minimum version updates since we haven't started releasing from master?14:54
dhellmannbknudson : ^^14:54
bknudsony, since we haven't released from master yet we can do whatever we want14:54
bknudsonwhatever we do here just affects what we do when we release master.14:55
ttxdhellmann: reviewing14:55
bknudsonI would prefer minor version #s here since it's reqs update.14:55
dhellmannttx, jroll : ironic-ui has python-ironicclient>=1.1 in, which means it installs that when we run "python --description" so that's why the announce email contains all of that garbage14:56
dhellmannjroll : do you have any idea why that dependency is in instead of requirements.txt?14:56
jrolldhellmann: ouch :(14:56
jrollI don't - betherly ?14:56
dhellmannit's in both, actually14:57
ttxI guess min update is an option there14:57
ttxyou should spell it out as X.Y+1.0 since so many people have issues with semver14:58
dhellmannok, let's go ahead with a minimum version14:58
dims+1 for X.Y+114:59
dhellmannhow about: X.Y.0 + 0.1.014:59
ttxnot sure that's clearer tbh14:59
dhellmann"increment the Y from X.Y.Z and reset Z to 0"15:00
dimsworks dhellmann15:00
dhellmannok, sending now15:00
ttxmaybe wait until lifeless is up before approving them so that he has a chance to chime in15:01
dhellmannapproving the releases?15:02
dhellmannor the requirements updates?15:02
mriedemdhellmann: i think we do minor version updates on stable branches if the requirements changes are higher minimum required versions of a dependency15:03
dhellmannmriedem : some of these are15:03
ttxI'll try to find some time to process nova rc2 in a few15:04
mriedemdhellmann: dims: re: " we want the automatic constraints updates turned off, but I think those only run in master already?" i think we want the u-c bot proposed updates disabled for stable/mitaka if they aren't already15:04
dhellmannmriedem : right, dims looked at that but if he reported back I missed what he said15:04
dhellmannttx: thanks15:04
mriedemdhellmann: dims: yeah, sorry, was in the nova meeting last hour15:04
dhellmannmriedem : np, that was a passive request for dims to repeat what he said earlier :-)15:05
*** lifeless has quit IRC15:13
*** david-lyle has quit IRC15:13
*** cody-somerville has quit IRC15:13
*** skraynev has quit IRC15:13
dimsdhellmann : mriedem : got side-tracked15:14
dimsdhellmann : mriedem : looking now15:14
gordcdhellmann: just a headsup, we'll need a ceilometer rc2 (i forgot to remove some entry_points)15:15
gordcis there a date i should request rc2 by?15:15
*** kzaitsev_mb has joined #openstack-release15:17
*** david-lyle has joined #openstack-release15:17
dhellmannjroll, betherly :
openstackLaunchpad bug 1561581 in Ironic UI "packaging instructions include extra dependencies" [Undecided,New]15:18
dhellmanngordc : next thursday:
*** armax has quit IRC15:19
gordcdhellmann: ack. i'll probably request it monday then to minimise rc requests15:20
*** armax has joined #openstack-release15:20
dhellmanngordc : ok15:21
ttxprocessing nova rc215:23
*** sdake_ has joined #openstack-release15:25
*** sdake has quit IRC15:25
betherlydhellmann: jroll I will definitely take a look at it and check it runs without being in Block booked on stuff today but will look Tuesday and ping you all re what I find15:26
dhellmannbetherly : I'm testing a patch locally now, stand by15:26
sdake_dhellmann there is a python dependnecy problem from python-extras and soemthing related to pbr on a fresh system15:26
betherlydhellmann: oh ok thanks15:26
sdake_dhellmann because of cisco policy, I am not permitted to submit changes outside of the openstack ecosystem without alot of hassle15:27
dhellmannsdake_ : "python-extras"?15:27
sdake_dhellmann ya the obvious solution is to install python-extras15:27
sdake_but i think the root of the problem is a dep is unaccounted for in a requirements.txt file15:27
dhellmannsdake_ : I don't know what that is15:27
sdake_pbr imports the chain of dependencies that end up using python extras15:28
clarkbsdake_: dhellmann looks like missing python dev headers?15:28
sdake_it can be obtained by yum intall python-extras15:28
sdake_i am nto sure what the pip equpvalent is15:28
sdake_clarkb yes he is definately missing xcode15:28
sdake_i just think its appropriate to get the requirements.txt files for whatever project is broken fixed15:29
sdake_but as I mentioned - cisco policy prevents that - or makes my life reallly difficult to do so15:29
clarkbthe fix is add dev headers I think15:29
*** lifeless has joined #openstack-release15:29
*** cody-somerville has joined #openstack-release15:29
*** skraynev has joined #openstack-release15:29
sdake_clarkb adding xcode may just install extras15:29
*** lifeless has quit IRC15:30
*** lifeless has joined #openstack-release15:30
jrolldhellmann: betherly: thanks15:30
jrollsdake_: clarkb: looks like just a missing python module, no?
clarkbyes because installcompilation failed?15:31
sdake_jroll yes i agree, suvvmit is the problem15:32
sdake_but it looks like it doesn't hae requirements.txt files15:32
jrollclarkb: looks like a warning to me15:32
sdake_clarkb that is a warning - it says it uses python code but its slower instead15:32
jrollsimplejson optimized if headers are available15:32
dhellmannjroll , betherly :
clarkboh its warlock failing a few lines below simplejson15:32
jrolldhellmann: lgtm15:33
sdake_the poitn is there is an unaccounted for dependency in subuit it appears, or its not getting installed via tox15:33
sdake_should i add it to kolla's requirements instead, or what is the correct fix exactly?15:33
dhellmannjroll , betherly : stable/mitaka backport:
patchbotdhellmann: patch 297220 - ironic-ui (stable/mitaka) - Remove python-ironicclient from setup_requires15:34
openstackgerritMerged openstack/releases: Tag Nova Mitaka RC2
sdake_jroll any thoughts?15:35
dhellmannsdake_ : it sounds like what clarkb is saying is warlock has the bad dependency, so I would think we should fix it  there15:35
jrollsdake_: it's in subunit's install_requires, which I think should be sufficient but maybe not?
sdake_dhellmann warlock just runs unopitimized without python development headers15:35
dhellmannhmm, no, it's not warlock. I see "positional"15:36
clarkbextras shows up in the list15:36
dhellmannline 316 in
clarkbthe log isnt exactly the clearest of things. It is running in some project and that fails to import extras15:37
sdake_more data, this isa fresh centos  install with pip install kolla/15:37
sdake_followed by tox -e releasenotes15:37
sdake_a third party is running the code to generate release notes in his env15:37
sdake_in my env, it works fine15:37
sdake_in his - its broken15:37
sdake_dhellmann your right - its positional15:38
sdake_316 ftw15:38
dhellmannsdake_ : looks like that's owned by morgan15:38
betherlyThanks for sorting them dhellmann15:38
dhellmannbetherly : thanks, we should plan on another mitaka release for you when that's done15:39
*** morgan has joined #openstack-release15:39
sdake_dhellmann but line 368 iports subunit which is the project which actually uses the dependency15:39
sdake_hey morgan15:39
sdake_just trying to sort out a missing dependency15:40
dhellmannmorgan : line 316 of starts an error reported trying to pip install kolla on a clean system15:40
sdake_in one of the dependencies we use15:40
dimsdhellmann : mriedem : (proposal bot)15:40
dhellmannsdake_ : you're right, maybe it really is subunit15:40
betherlydhellmann: when they've merged do I need to submit a release patch for 1.2?15:40
sdake_not pip install kolla15:40
sdake_tox -e releasenotes15:40
dhellmannbetherly : yes, and see also my email to -dev about the requirements updates in case you have one of those patches (we should release both together)15:40
dhellmannsdake_ : oops, sorry15:40
morgandhellmann: weird15:41
clarkbI think it is executing code at install time that shouldnt run until post install?15:41
clarkbso the extras module cant be found yet15:41
dhellmannclarkb : yeah, pip install testrepository gives me extras15:42
sdake_hmm maybe testrepository is a missing dependency from kolla15:42
sdake_should that be in kolla? :)15:42
morgani mean, positional does pbr things...15:43
dhellmannmorgan : oh, does it?15:43
morgandhellmann: yes. it uses pbr15:43
morganor it should be using it15:43
morganthe code is extremely simple15:43
dhellmannI see it using pbr in, is that what you mean?15:43
dhellmannthat shouldn't cause this15:44
morganpositional is insanely simple15:44
sdake_kolla has testrepository15:44
clarkbok how old is the tox/virtualenv in use?15:44
morgandhellmann: i don't know how it could be causing an issue unless there is something wonky with pbr15:44
clarkbcould be a bad old setupyools.behavior15:44
dhellmannclarkb : good call15:45
sdake_clarkb i am not sure15:45
dhellmannsdake_ : find out if they installed setuptools from a system package, or from pip15:45
*** sbezverk has joined #openstack-release15:45
sdake_clarkb i am haing sbezverk join the channel now15:45
sbezverkmorning folks15:45
dhellmannpip, pbr, tox, virtualenv all need to be current and not system packages (mostly because those are rarely current)15:45
clarkbdhellmann: sdake_ tox depends on virtualenv which bundles setuptools15:45
sdake_sbezverk run rpm -qi setuptools \ fpaste15:45
sdake_or python-setuptoools15:45
dhellmannwell, if you're installing setuptools from rpm that's probably your issue right there15:46
sbezverkFYI I am on ubuntu15:46
dhellmannthe debs there are also usually out of date -- we recommend developers install python dev tools using pip15:46
sdake_sbezverk ok well tell us if you using packaged version of setup tools or pip installed version15:46
*** doug-fish has joined #openstack-release15:47
sdake_folks thanks for all the debug - my main concern is I wan tto make sure there isn't a missing deependency somewhere in our dep chain15:47
ttxdhellmann: I propose we just reply to the RC1 email to announce RC2s, rather than start a new thread15:47
dhellmannttx: makes sense15:47
dhellmannsdake_ : sure. We have pretty minimal images in our gate, specifically for reasons like this.15:48
sdake_dhellmann fwiw the gate works15:48
dhellmannright, that's what I mean. It's working in the gate, and on your system and mine, so I think this is an issue with sbezverk's system and not the packaging instructions15:48
sdake_dhellmann got it makes sense15:49
sbezverkdhellmann very possible, I pasted the list of installed modules15:49
dhellmannsbezverk : latest tox is 2.3.1, latest setuptools is 20.3.1, so I'd try upgrading those15:49
sdake_sbezverk aey ou using apt installed setuptoools15:49
sbezverkcould you identify which one is not supported15:49
clarkbsbezverk: dhellmann specifically oyu have to upgrade virtualenv for tox to use newer setuptools since virtualenv bundles setuptools15:50
dhellmannsbezverk : the general rule is, when you are doing python development for openstack projects do not install the tools for that from system packages. Use to install pip, then use pip to install the other tools you need15:50
dhellmannclarkb : yeah, thanks, I missed that one15:50
dhellmannsbezverk : the latest virtualenv is 15.0.115:51
dhellmannso you can see that lots of those packages are *far* out of date15:51
sdake_dhellmann ++ thanks :)15:52
dhellmannsdake_ : clarkb figured it out :-)15:52
sdake_clarkb ++ :)15:52
sdake_sbezverk do you need further assistance in getting your system updated?15:54
sdake_if so, lets go over to #kolla and go through it there15:54
sdake_apologies all for the idea that this was an unaccounted for dependency - i thought sbezverk was on centos where all this stuf fworks with system packaging :)15:55
dhellmannsdake_ : np, that's certainly what it looked like15:56
sbezverkupdating all these modules broke pip somehow.. Is there a list with precise required version of required components15:56
sbezverkI will try to recover it offline15:56
sdake_use the get-pip shell tool15:56
*** palendae has joined #openstack-release16:12
*** mriedem is now known as mriedem_snow16:22
palendaeI have a question regarding reno and projects like openstack-ansible, which have their own subprojects - when submitting patches to the individual role repositories, release notes currently have to be duplicated in order to show up in both OSA and the role repository. Adding roll up functionality to reno would help with this, but I'm wondering if that's generally desirable for others16:23
*** sheeprine has quit IRC16:25
*** vgridnev has quit IRC16:25
sbezverkdhellmann I am still having an issue generating release notes, please see this paste:
sdake_hey folks sbezverk still having same problem after upgrading all his deps16:26
clarkbsdake_: sbezverk make sure you run tox -r -e whatever16:26
sbezverkI have updated every component in pip16:26
clarkbto rebuild the virtualenv16:26
sdake_clarkb thanks i dind't think of that16:26
sbezverkclarkb thank you, will try that now16:27
sdake_sbezverk two options rm -rf .tox or tox -r -e releasenotes16:27
dimsdhellmann : am done with my meetings for the day, reading scroll back16:28
*** kzaitsev_mb has quit IRC16:28
*** vgridnev has joined #openstack-release16:28
sbezverkclakrb same issue, see this paste:
sdake_sbezverk can we get a pip show to validate your deps are all up to date16:30
*** sheeprine has joined #openstack-release16:30
sdake_sbezverk i am not python wizard enough to knw, but folks in this channel can give a qiuck eval16:30
sbezverksdake_ do you mean pip list?16:30
sdake_pip show should show everything iI think16:30
sdake_but maybe its pip list16:30
clarkbyes pip list16:30
sdake_i'm ony at 8000 hours of experience with python16:30
clarkbthat will include setuptools which freeze does not16:31
sdake_so not quite expert level yet16:31
sbezverksdake_ here you go
sdake_maybel ess, like 6k hours16:31
sdake_clarkb any ideas on the above paste?16:32
sdake_six is definately old16:32
sdake_pbr may be old16:32
sdake_requests is s uper old16:32
clarkbpbr looks up to date16:32
sdake_oh- testtools16:32
clarkbas do setuptools virtualenv and pip16:32
sdake_testtools could be old no?16:33
sdake_is extras only at 0.0.3?16:34
*** sdake_ is now known as sdake16:34
clarkbya but thats not in the virtualenv so we only really care about the bootstrap a virtualenv code16:34
sdakesbezverk do this - rm -rf .tox in the kolla directory16:35
clarkbthe other possibility is stale pbr in the repo itself, you might try with a clean checkout if not already16:35
sbezverksdake I think you are looking at wrong place16:35
sbezverklog said that some .h files are missing16:35
sdakeok well that is an otpimization, but lets fix that16:36
sdakeinsall the python-dev package via apt16:36
sbezverksdake done it now rerunning tox16:36
*** vgridnev has quit IRC16:36
sbezverksdake it is better but still errors, now it did not find yaml.h16:37
clarkbfwiw I just ran that tox command on my local ubuntu machine and had no issues16:37
sbezverkdo you know from the top of your head which dev tools provide this header?16:37
clarkbsbezverk: python-dev and libyaml-dev16:37
sdakeyaml-dev possly?16:37
clarkbbut those were listed as warnings so we ignored them initially, though its possible that they claim to be warnings but result in fails16:38
sdakeclarkb yup might as well fix em ;)16:38
sbezverkclarkb sdake still fails different error though
clarkbthat doesn't look like complete output?16:42
clarkbsome of the compiles can be very noisy :/16:42
sdakesbezverk where is th full log please16:42
sdakesbezverk don't forget to remove .tox16:43
sbezverksdake clarkb the log gets cut by paste site. do you want me to email it to you?16:44
sdakepate on fedorapeopel.org16:45
sdakeor pastebin16:45
sdakeparather paste.fedoraproject.org16:46
clarkbits the same error at the end, no module named extras16:48
clarkbI have no idea honestly16:48
sdakesbezverk cd /usr/lib/pythoon*/site-packages16:49
sdakels -ld extra* | paste16:50
sbezverksdake I do not have site-packages folder16:52
sdakeclarkb what i'm thinking is he is two extrs packages installed one distro and one pip16:52
sdakei dont know layout of ubuntu becausei use centos for dev16:52
sdakeany tips on where to look?16:52
clarkbthat shouldn't matter due to the virtualenv16:53
clarkbunless kolla allows site packages, let me look16:53
clarkbdoesn't appear to16:53
sbezverksdake I found one here: /nobackup/sbezverk/iscsi/kolla/.tox/releasenotes/lib/python2.7/site-packages16:53
sdakeis there an extrs package in that directory?16:54
*** odyssey4me has quit IRC16:55
sbezverksdake nope16:55
*** odyssey4me has joined #openstack-release16:55
sdakesbezverk add extrs to test-requriemetns.txt in kola16:56
sdakethis isn't a proper solution but i wan tto see if it makes it work16:56
sbezverksdake found extras here /usr/lib/python2.7/dist-packages/extras16:56
sdakerm .tox as well16:56
dhellmannhey, guys, could you debug this in another channel, please?16:57
sdakedhellmann will do16:57
sdakesbezverk back to kolla16:57
dhellmannthanks, sorry16:57
sdakedhsorry for noise16:57
sdakedhellmann no reason to apoologize16:57
sdakei originally thought it was a dep problem in our dep chain but i think its just sbezverk environmental16:57
sdakedhellmann hence the escalation to this channel16:57
dhellmannyep, of course, np there16:58
*** sridhar_ram has joined #openstack-release17:00
*** openstackgerrit has quit IRC17:01
*** openstackgerrit has joined #openstack-release17:01
odyssey4medhellmann back to palendae's question17:02
*** kzaitsev_mb has joined #openstack-release17:02
odyssey4meis there a way, right now, that we'd be able to do some sort of release note roll-up between repositories?17:02
odyssey4merepo A contains docs, release notes and code. repo A publishes those. repo A consumes repo B. repo B has release notes (kinda like a library). Could we work out a way for repo A to consolidate release notes from repo B and present them as a uniform set?17:04
ttxdhellmann: ok, Nova RC2 posted, see template for RC2 announces there17:19
ttxHopefully kept the msgid and threads properly17:19
*** gordc has quit IRC17:29
ttxquick review of stable/mitaka changes before closing crtazyday17:30
*** vgridnev has joined #openstack-release17:31
ttxso far no violation of the "merge in master first" rule17:33
ttxalright, calling it a day17:34
openstackgerritArmando Migliaccio proposed openstack/releases: Neutron Mitaka RC2 deliverables
clarkbgrenade is on its way to understanding mitaka as well17:35
*** sridhar_ram has quit IRC17:35
*** sridhar_ram has joined #openstack-release17:36
dhellmannttx: thanks17:38
*** pcaruana has quit IRC17:40
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/releases: Release OpenStack-Ansible Kilo 11.2.12 / Liberty 12.0.9
*** kzaitsev_mb has quit IRC17:50
odyssey4medhellmann heh, that one's fun - it would appear that two releases at once doesn't work so well :) let me split them up18:04
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/releases: Release OpenStack-Ansible Kilo 11.2.12
*** sdake_ has joined #openstack-release18:07
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/releases: Release OpenStack-Ansible Liberty 12.0.9
dhellmannodyssey4me : did it fail? as long as there aren't multiple releases in the same file it should work18:08
dhellmannoh, independent, yeah, that won't work, we'll have to merge one and then recheck the other18:09
odyssey4medhellmann yeah, it was two in the same file - so the analysis output was only for one of them18:09
dhellmannyeah, it skips to the last one18:09
odyssey4meI've split them up - and they won't conflict with each other (different place in the file)18:09
*** sdake has quit IRC18:10
dhellmanndid you submit them as a series?18:13
odyssey4medhellmann nope - independent patches18:13
dhellmannok. I'm not sure inserting something into the middle of the file actually works18:13
odyssey4meoh dear18:14
dhellmannwe should make it, but I don't think that's a case we've dealt with yet18:14
odyssey4meoriginally we were in the series thing, but got moved to independent18:14
dhellmannyeah, ttx and I discussed that because of your release model18:14
dhellmannwe might need to rethink that18:14
odyssey4mewe really should be cycle-with-intermediary, but didn't make the cut-off date for requesting the change of release model18:14
odyssey4meI'm happy to submit a request to governance to change it if that would help?18:15
odyssey4meAlthough as I recall there are specific windows to do that.18:15
dhellmannyeah, go ahead and do that, and I'll revert the change that merged the files and then we can apply your releases on top of that change18:15
odyssey4meok cool18:16
dhellmannodyssey4me : give me the link to the governance patch when you have it, so I can put it in the commit message for the revert18:16
odyssey4mewill do18:16
*** mriedem_snow is now known as mriedem18:20
odyssey4medhellmann does that make sense?
*** daemontool has quit IRC18:32
openstackgerritDoug Hellmann proposed openstack/releases: Revert "move openstack-ansible under the _independent directory"
dhellmannodyssey4me : yes18:33
odyssey4meawesome, thanks18:34
dimsdhellmann : we don't need to wait for governance model changes?18:35
dhellmannodyssey4me : I'll wait and let dims and ttx have a chance to look at both of our patches before continuing, but if you want to submit your new tags as follow-ups to the revert that would speed things along18:35
dimsy was just reading both dhellmann18:35
dhellmanndims : no, the review timeline for those is pretty long (a week for lazy consensus)18:35
odyssey4meok, let me get on that so long18:35
dhellmannthe intent is there, as long as we don't downvote the governance change it's fine18:36
*** gordc has joined #openstack-release18:36
odyssey4meI expect that if the governance change is downvoted, then the release changes can always be resolved.18:36
dimsodyssey4me : +218:36
dhellmannodyssey4me : yeah, we'll just have to make the tools smarter :-)18:38
palendaeSpeaking of smarter tools :)18:38
palendaeUnless I'm misreading the backlog, have you considered the question about release notes from subprojects being rolled/bubbled up into a parent project, dhellmann?18:39
dhellmannpalendae : that's not something we've considered. what's the use case?18:40
*** vgridnev has quit IRC18:40
*** sridhar_ram1 has joined #openstack-release18:40
palendaeI'll steal odyssey4me's wording from above: repo A contains docs, release notes and code. repo A publishes those. repo A consumes repo B. repo B has release notes (kinda like a library). Could we work out a way for repo A to consolidate release notes from repo B and present them as a uniform set?18:40
palendaeIn this case, Repo A is openstack-ansible, repo B is a role that it pulls in (
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/releases: Release OpenStack-Ansible Kilo 11.2.12
*** sridhar_ram has quit IRC18:41
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/releases: Release OpenStack-Ansible Liberty 12.0.9
dhellmannpalendae : one challenge, maybe not a blocker, is that reno uses the source repo to determine what version # to associate with a note18:44
palendaeSo it would be the version number/tag of the repository the note is in?18:46
dhellmannthat's what you would want, right?18:46
dhellmannyou would want the collected notes to say things like "role X version A.B.C has note foo"18:46
palendaeI do think that makes sense, I don't know if it's what others would want :) But it makes sense for me to not only denote the release notes at the OSA level, but the versions included18:47
palendaeSo basically OSA becomes an aggregate18:47
dhellmannhow would you different role versions be organized in the OSA release notes? by OSA version of some sort?18:48
palendaeI think a release of OSA would include 1-and-only-1 version of the role18:49
dhellmannhow does reno know what that version is?18:49
dhellmannfor that matter, how does anything else know?18:49
palendaeAs I understand odyssey4me's plan, that'll be pinned in
palendaeWhich I realize reno doesn't consume now18:50
dhellmannyeah, something could use that to drive reno though18:50
odyssey4meyeah, so the integrated release will have a SHA pinned relationship with the role.18:50
odyssey4meeach role is consumable on its own - so it makes sense for it to have its own release notes18:51
palendaeI think there was a larger discussion regarding the role versioning, which unfortunately I haven't been too involved with. That output's probably related to this18:51
odyssey4meOSA ideally would aggregate the release notes, but the release notes would be organised by the integrated release tags for that aggregated set18:51
odyssey4meif that seems plausible enough to do, I'd appreciate it if you could coach palendae enough to work out a PoC18:52
palendaeI'm guessing reno itself wouldn't want to do this, but the pipeline would need to be flexible enough to have some sort of hook18:53
dhellmannyou might be able to build something using the existing report command18:54
dhellmannyou would have to clone each repo, then run something like "reno report --version $v $repo"18:54
dhellmannwell, that would give you one rst file per repo with the repo's version number18:55
dhellmannthat wouldn't give you something easy to merge together, though18:55
odyssey4medhellmann if I understand it correctly, while reno handles the heavy lifting it's sphinx that does the publishing right?18:56
dhellmannthe new 'cache' command builds a yaml file, so you might want to use that
palendaeodyssey4me: reno collects the ReST out of the YAML18:56
palendaeSphinx renders the ReST18:56
dhellmannodyssey4me : that's right. reno extracts the notes and formats them as rst, then sphinx converts that to html or whatever18:56
odyssey4meah, that makes sense18:56
palendaeOpenstack's current sphinx invocation isn't super flexible18:57
dhellmannpalendae : the cache command is intended to build a single yaml file for us to include in a dist where the git history won't be available downstream18:57
dhellmannif you wrote something to read multiple of such files, they could then be combined and rendered together18:58
lifelessttx: url's ?18:58
dhellmannyou'll need a custom release notes build job to check out all of the repos, build the yaml file, and put it somewhere18:58
palendaeOk, that's a great start18:59
dhellmannit might be better, rather than doing that when the release notes are built, to do it when a release note is added to another project and submit the results as  a patch to the central release notes project18:59
dhellmannwe're planning something similar for automating configuration reference guides18:59
dhellmannthat's also how the requirements updates work, so there's a nice pattern there18:59
palendaeSo an automated commit is made?18:59
dhellmannan automated patch is submitted, but it still has to be reviewed18:59
palendaeOh, ok19:00
palendaeThis is already running somewhere?19:00
palendaeOr it's planned?19:00
dhellmannthe requirements updates are, but the config option thing is planned19:00
odyssey4medhellmann that's perfectly acceptable - we're doing that manually now19:00
palendaeYeah, the current solution is to copy the reno file out19:00
palendaeAnd manually submit 2 patches19:00
odyssey4meso there's just a post merge job that pulls a part of the patch out and submits it to a designated repo19:01
dhellmannpalendae : doing it as a post-merge job also has the benefit of making the job easier to write, because you only need to check out 2 repos19:01
palendaeIf I'm following, just OSA and that role, right?19:01
dhellmannodyssey4me : yeah. the tricky bit will be updating an existing patch if it exists, to avoid merge conflicts, but the requirements updater already does that so you may be able to reuse the logic19:01
dhellmannthat's right19:02
dhellmannyou'd attach the job to the post-merge queue for the role repo and the job would check out OSA so it can submit a patch there19:02
*** kzaitsev_mb has joined #openstack-release19:03
palendaeOk, makes sense. Then the notes are duplicated, but at least in a relatively automated way19:03
lifelessttx: (It's already easter here, but I'll check by a couple of times during it...)19:04
dhellmannpalendae : as a first step, you could build tools to do that outside of CI, and then we could work on adjusting them to work in gate jobs19:04
*** cody-somerville has quit IRC19:04
dhellmannlifeless : hang on, let me find what we were talking about...19:04
palendaeOk, I'll see if I can take a stab at something like that19:05
dhellmannlifeless : ok, I have the context again: We branched openstack/requirements master to create stable/mitaka. That triggered the requirements update bot to submit a bunch of patches against other projects that also had stable/mitaka that did not match the new requirements:
dhellmannlifeless : we recommended that projects merge those changes and then submit minor version releasese from their stable branches so all projects are in sync and clear before we declare mitaka "done"19:06
lifelessyeah, eventual consistency. +119:06
odyssey4mepalendae if you need help navigating the infra jobs, let me know - we'll need to instrument the role repositories for reno jobs which isn't hard, but I expect that'll be needed19:06
dhellmannlifeless : ttx wanted your thoughts on the use of a minor version update there, I think. We have used patch releases in the past, but since we don't have any new releases from master yet going with a minor version update seemed to communicate the nature of the changes better (some have new lower bound version requirements)19:07
*** daemontool has joined #openstack-release19:07
*** vgridnev has joined #openstack-release19:07
odyssey4mepalendae I expect that pabelanger will also be happy to assist and would probably like to know about anything affecting the ansible roles, as the jobs touch his too.19:07
lifelessdhellmann: Perhaps I'm not clear what you mean there19:07
dhellmannodyssey4me , palendae : check for existing patches with the "add-reno" topic for examples of doing that. It's highly repetitive, so once you get one patch right you should be able to mostly copy those files into the other repos.19:07
odyssey4medhellmann thanks for the pointers and advice, as always19:07
lifelessdhellmann: are you saying libraries/clients that have already done a mitaka release do a new one?19:07
dhellmannlifeless : yes19:08
palendaeodyssey4me: Yeah, I've added some in the past. Mostly going to be figuring out plumbing git, and I'm gonna dig through project-config19:08
lifelessdhellmann: to get the new requirements out there?19:08
dhellmannlifeless : right. we wouldn't raise the minimum required version of the libs in the stable branch, but we would release everything that has a requirements update so they are all in sync19:09
dhellmannand I guess update the constraints, to go with that19:09
lifelessdhellmann: I don't think those additional releases are needed19:10
lifelessdhellmann: they're being used in concert with other libraries which have those higher mininums already19:10
dhellmannlifeless :
lifelessand we know pip is just plain incapable of actually handling variation here at all - which is why we use and recommend the use of a constraints file for deployments19:11
dhellmannsure. the thing I was trying to avoid was in a few weeks when we start having releases from master, we didn't want anyone concerned about releasing patch releases with version updates from the stable branch19:11
dhellmannwe sort of talked ourselves into calling those bugs in the past, but we have a chance to use the right semver rules here so I was going to take it19:12
dhellmannso it's a bit of an extra thing, and not critical for anyone to package, but it puts us in a clean, good, well-understood state heading into newton19:12
lifelessI think where there are major version changes to reqs we definitely have to propogate that19:13
lifelessminor, as I recall, we concluded there was no formula19:13
lifelesslibrary A's minor version to add a feature, is not user B's addition of a feature19:13
dhellmannI'm pretty sure there are no major versions but we do have cases of A needing newer minor versions of B19:13
dhellmannwe'll have to review each release as usual, the point is really that we'd allow for something other than a patch level update in the stable branch *this time*19:14
dhellmannsome of them are just test-requirements updates, and those don't really require a release at all, but we can sort that out when the release is actually requested19:14
lifelessI agree now is the time to do it19:18
lifelessthose releases won't be reachable from masters history19:18
lifelessso this will require tags or sem-ver: headers on master to actually get it ahead of mitaka19:18
dhellmanndo we need to worry about that before there's something to release on master?19:20
lifeless(because regular commits won't outstrip a minor release)19:20
*** cody-somerville has joined #openstack-release19:20
dhellmannthere's the ongoing discussion of that on the ML19:20
lifelessdhellmann: I don't think we want whats on PyPI to be greater than whats on master19:20
dhellmannhmm, yeah19:20
lifelessdhellmann: which might be a corner case we missed during the discussion, come to think og it19:20
lifelessI'm just processing that thread atm19:20
dhellmannyeah, I'm not sure we considered this when we talked about it19:21
dhellmannor if we did, we said "oh, we'll only ever release patch levels from stable branches"19:21
dhellmannwhich would still let us outpace master, of course19:21
dhellmannwhat's the concrete issue that could come up if the mitaka branch has a version > unreleased master?19:22
*** daemontool has quit IRC19:25
lifelessI just hit enter on an email about it19:28
lifelesspip install -U foo19:28
lifelesswhere foo depends on bar19:28
lifelessand bar is from master git19:28
lifelesswill 'upgrade' bar to bar from PyPI if master git is < PyPI.19:29
dhellmannwhen might that happen?19:32
dhellmannsomeone has a git url in their requirements list?19:33
lifelessI think its happened right now19:33
lifelessdhellmann: pip install .19:33
lifelessdhellmann: devstack uses constraints so isn't a concern19:33
lifelessdhellmann: folk adhocing things is where it would matter, because something they do by hand could get unwound19:33
odyssey4medhellmann verified - that's good to go whenever you're ready19:39
odyssey4medhellmann also verified - good to go whenever you're ready19:43
dhellmannlifeless : ok, so I'm going to agree with ttx's proposal that we hold off on approving releases until we give this more thought and see where the ML thread takes us19:50
dhellmannodyssey4me : ack, I'll take a look at those tomorrow when my head is clear19:50
odyssey4methanks dhellmann19:51
AJaegerdhellmann, dims : Did you really want requirements jobs not to run on stable/mitaka? - would like to see an ack by dhellmann on it...19:58
dhellmannAJaeger : yes, automatic updates should only happen on master19:59
dhellmannAJaeger : we may reverse that at some point, but for now it's going to be easier to keep things sane if we do it manually19:59
AJaegerdhellmann: ok, will +2 then and comment on your ack.20:00
dhellmannAJaeger : thanks for checking in, I should have +1 that when dims submitted it20:00
*** amrith is now known as _amrith_20:06
*** sdake has joined #openstack-release20:07
*** sdake_ has quit IRC20:07
*** sdake_ has joined #openstack-release20:10
*** sdake has quit IRC20:12
dhellmannI'm going to drop off a bit early and see if I can get rid of this headache20:12
lifelessdhellmann: kk20:13
lifelessdhellmann: good luck with the headache20:13
dimsgood night dhellmann20:16
*** kzaitsev_mb has quit IRC20:22
*** sridhar_ram1 is now known as sridhar_ram20:24
*** sdake has joined #openstack-release20:30
openstackgerritJohn Dickinson proposed openstack/releases: Swift 2.7.0 release
notmynamettx: dhellmann: ^ swift mitaka release20:31
*** sdake_ has quit IRC20:33
*** openstackgerrit has quit IRC20:48
*** openstackgerrit has joined #openstack-release20:48
*** kzaitsev_mb has joined #openstack-release20:50
*** doug-fis_ has joined #openstack-release20:57
*** doug-fish has quit IRC20:59
*** sdague has quit IRC20:59
openstackgerritJim Rollenhagen proposed openstack/releases: ironic-lib 1.2.0
*** sdake has quit IRC21:01
*** kzaitsev_mb has quit IRC21:04
*** doug-fis_ has quit IRC21:05
*** sileht has quit IRC21:07
prometheanfirewhen are upgrade docs going to be available? day of release, sooner, later?21:08
*** sileht has joined #openstack-release21:08
openstackgerritBrant Knudson proposed openstack/releases: Keystone mitaka library update releases
clarkbits usually a while later as the docs team works through the process and gets it tested and written up21:10
stevemarbknudson: did someone ask for that ^21:11
bknudsonstevemar: on the mailing list21:11
stevemarbknudson: oh okay, i am severely behind today21:12
bknudsonstevemar: you need to stop working on your superman costume21:12
stevemarbknudson: only if you switch out of your batman one21:12
stevemarbknudson: no keystoneclient?21:13
*** _amrith_ is now known as amrith21:13
stevemarthen prepare release requests for the affected projects as soon as possible21:14
bknudsonstevemar: -- no keystoneclient21:14
stevemarbknudson: i wonder why, it should have oslo.config21:14
stevemarand oslo.utils21:15
bknudsonalready has it -
stevemarbknudson: looks like it was fine
stevemarbknudson:  want to add in pycadf to that release review too?21:16
stevemari just punted it through21:16
stevemarit should merge very soon21:16
stevemarits not part of integrated gate21:17
bknudsonI'll need to wait until it merges to get the commit ID21:17
stevemarbknudson: but dims and doug won't be releasing the libs any time soon21:17
bknudsonwe need to get the release requests ready ASAP and they just get to sit around??21:18
*** gordc has quit IRC21:18
stevemarit's good to be king21:19
*** kzaitsev_mb has joined #openstack-release21:21
openstackgerritSean McGinnis proposed openstack/releases: Release os-brick 1.1.1
*** armax has quit IRC21:34
*** armax has joined #openstack-release21:34
*** devananda has quit IRC21:35
*** openstack has joined #openstack-release21:49
*** openstackgerrit has joined #openstack-release21:49
betherlyhi all is there anyone around who can help with the update of the requirements patch so i can re - release ironic-ui?21:56
*** sridhar_ram has joined #openstack-release22:00
*** skraynev has joined #openstack-release22:00
openstackgerritBeth Elwell proposed openstack/releases: Release ironic-ui 1.2.0
patchbotbetherly: patch 297386 - releases - Release ironic-ui 1.2.022:11
jrollbetherly: +1'd with a comment22:13
jrollyou should totally look into using reno for release notes btw :)22:13
betherlyoh ok! thanks will do22:13
* betherly adds that to neverending research pile22:13
betherlyjroll: im heading off to bed pretty soon as its 10pm here and off to surf tomorrow (YAY) if you want it to merge any sooner and it needs to be 1.1.1 would you be able to make that change for me and amend the patch so it can merge before next tuesday?22:15
jrollbetherly: yeah, I'll wait for release team to comment, have fun surfing :)22:16
betherlyjroll: awesome thanks!22:16
stevemarbknudson: pycadf should be merged soon22:16
*** kzaitsev_mb has quit IRC22:18
*** sigmavirus24 is now known as sigmavirus24_awa22:31
openstackgerritBrant Knudson proposed openstack/releases: Keystone mitaka library update releases
openstackgerritBrant Knudson proposed openstack/releases: Keystone mitaka library update releases
*** sdake has joined #openstack-release22:58
*** sdake_ has joined #openstack-release23:17
*** sdake has quit IRC23:18
openstackgerritJim Rollenhagen proposed openstack/releases: python-ironicclient 1.3.0
*** sdake has joined #openstack-release23:28
*** sdake_ has quit IRC23:28
openstackgerritJim Rollenhagen proposed openstack/releases: python-ironic-inspector-client 1.6.0
sdakewhere are the releaes notes published once you have a releasenotes job in jenkins?23:38
sdakedoes it upblished unreleased?23:47
jrollyeah, it should23:48
sdakeso just need a commit to test it looks like23:49
jrollit's a post job, so there's a delay between merge and publish23:49
*** sbezverk has quit IRC23:54

Generated by 2.14.0 by Marius Gedminas - find it at!