Friday, 2016-01-22

tristanCDaviey: well I just noticed the review wasn't merged only after you changed the task status, the exception request must have slip through the net00:02
DavieytristanC: Oh well.. it'll get pulled into the next one now :)00:06
bswartzdhellmann: I noticed you haven't workflowed the manila release yet -- I'd like to change the commit if that's okay with you -- some more things managed to get thru the gate00:07
tristanCDaviey: phew, that's fine then... So in theory we could do another release with that change only right ?00:09
DavieytristanC: Hmm.. i think we have the next release tentatively scheduled for May00:10
tristanCoh ok, then I misunderstood last summit discussion about releasing/tagging each backport. or maybe this is only implemented starting at liberty00:15
tristanCanyway for that particular bug, as long as the release note doesn't mark it as tag, it's totally fine since a security note as already been published about it00:18
tristanCmark it as fixed*00:18
openstackgerritDoug Hellmann proposed openstack/releases: Release Manila M-2 milestone  https://review.openstack.org/27103300:25
dhellmannbswartz : I just saw your note. Let me know if you still want to change the sha00:26
dhellmanndaemontool_ : you've submitted it on time, though we need to get it to validate00:26
dhellmanndaemontool_ : it appears someone has already tagged your repo, incorrectly00:27
*** yarkot has joined #openstack-release00:29
dhellmannttx: I held off on any m2 requests that would result in actual releases because of the gate issues this week. We can cut those Friday if you think it won't be a problem, or wait for Monday.00:33
dhellmannttx, dims_ : it would also be good to land any of the tool changes necessary before landing any of the release requests00:34
DavieytristanC: Yeah.. the prior releases are still being treated on the old sucky process.00:35
dims_dhellmann : i see 4 changes in release-tools repo looking00:35
dhellmanndims_ : yeah, I agree with mriedem about the convenience script, so I'll mark that WIP00:36
dims_dhellmann : ack, will let the others in00:37
dims_dhellmann : should be merging now00:38
dhellmanndims_ : thanks!00:39
openstackgerritMerged openstack-infra/release-tools: Optimize announce subject line  https://review.openstack.org/27092300:39
openstackgerritMerged openstack-infra/release-tools: ignore deleted files when listing deliverable changes  https://review.openstack.org/27091000:39
tristanCDaviey: makes sense, thanks!00:39
dhellmanndims_ : I'm assuming you're ok with the requested oslo releases, for early next week?00:39
openstackgerritMerged openstack-infra/release-tools: make announce.sh more robust for first releases  https://review.openstack.org/27101100:40
dhellmanndims_ (repeating comment to ttx from earlier): I held off on any m2 requests that would result in actual releases because of the gate issues this week. We can cut those Friday if you think it won't be a problem, or wait for Monday.00:40
dims_dhellmann : sounds good00:41
dhellmanngiven that, I think I've done everything I can tonight so I'm going to go see about some food00:41
dims_:) good night dhellmann00:41
dhellmanng'niite, dims_ !00:41
*** lane_kong has joined #openstack-release00:41
openstackgerritBen Swartzlander proposed openstack/releases: Release Manila M-2 milestone  https://review.openstack.org/27103301:03
bswartzdhellmann: ^ new sha posted -- thanks for waiting01:03
*** doug-fish has quit IRC01:04
*** doug-fish has joined #openstack-release01:05
*** doug-fish has quit IRC01:06
*** doug-fish has joined #openstack-release01:06
*** mriedem has joined #openstack-release01:11
*** yarkot_ has joined #openstack-release01:18
*** yarkot_ has quit IRC01:29
*** dims__ has joined #openstack-release02:04
*** dims_ has quit IRC02:06
*** mriedem has quit IRC02:12
*** doug-fish has quit IRC02:20
*** doug-fish has joined #openstack-release02:21
*** doug-fish has quit IRC02:21
*** doug-fish has joined #openstack-release02:21
*** [1]Thelo has joined #openstack-release02:34
*** Thelo has quit IRC02:36
*** [1]Thelo is now known as Thelo02:36
*** doug-fish has quit IRC02:50
*** Qiming has joined #openstack-release03:00
*** doug-fish has joined #openstack-release03:50
*** doug-fish has quit IRC04:00
*** dims__ has quit IRC04:08
*** daemontool_ has quit IRC04:12
*** daemontool_ has joined #openstack-release04:13
*** daemontool_ has quit IRC04:18
*** doug-fish has joined #openstack-release05:32
*** doug-fish has quit IRC05:32
*** SlickNik has quit IRC05:43
*** vipuls has quit IRC05:47
*** SlickNik has joined #openstack-release06:01
*** SlickNik has quit IRC06:01
*** SlickNik has joined #openstack-release06:07
openstackgerritSergey Kraynev proposed openstack/releases: Release python-heatclient 0.9.0  https://review.openstack.org/27117308:01
*** daemontool has joined #openstack-release08:18
openstackgerritFausto Marzi proposed openstack/releases: openstack/freezer openstack/freezer-api 2.0.0.0b2 Mitaka 2  https://review.openstack.org/27107008:28
*** daemontool has quit IRC08:48
*** daemontool has joined #openstack-release08:48
*** daemontool_ has joined #openstack-release09:03
*** daemontool has quit IRC09:06
openstackgerritMerged openstack/releases: Release Manila M-2 milestone  https://review.openstack.org/27103309:18
daemontool_ttx, re: https://review.openstack.org/#/c/271070/09:22
ttxyes09:22
daemontool_when should I full release?09:22
daemontool_after the other services released all the milestones?09:23
ttxthe model you picked let you release whenever you want. We just take the last release in a cycle to be part of the final set of Mitaka releases09:23
ttxIf you prefer to release once at the end of the cycle and do milestones, you should update your release model09:23
ttxalthough it is a bit late to do so09:24
daemontool_ok, that's not a prob, how do you take the last release in a cycle?09:24
daemontool_from the tag?09:24
daemontool_is there anything is required from our side?09:24
ttxif you follow intermediary, you should make regular releases... and plan to do one a few weeks before the end of the cycle09:25
ttxso that we have a fresh one to include in the "mitaka" release09:25
* ttx looks at freezer tag history09:25
ttxoh, you did the tag already09:26
ttxhrm09:26
ttxat this stage you may want to switch to cycle-with-milestones then09:26
ttxsince that is what you followed09:27
ttxdaemontool_: what do you want ?09:27
daemontool_ok09:27
daemontool_I'd like at this stage for mitaka09:27
daemontool_be part of the release is possible09:27
daemontool_and from the next cycle follow cycle-with-milestones09:27
daemontool_s/is/if09:28
daemontool_so to be part of mitaka now do I need to do anything else?09:28
ttxSo... in both cases you are part of the mitaka release. The question is, do you want to follow a feature freeze around mitaka-3 and follow the common dev cycle and make a final release...09:28
ttxor do you want to do plenty of small releases09:28
daemontool_yes09:28
daemontool_I want to follow a feature freezer09:29
ttxgiven the maturity of the project, I think following milestones is the right choice09:29
daemontool_around mitaka-309:29
ttxok09:29
daemontool_yep09:29
ttxso we need to fix the governance repo to match that09:29
daemontool_ok I'll update that09:29
ttxAlso, the question of deliverables.09:29
daemontool_right now09:29
daemontool_I'll check that soon09:29
ttxyou have two repos09:29
ttxfreezer and freezer-api.09:29
daemontool_ah ok09:29
daemontool_yes09:29
ttxAre they released separately with different version numbers ?09:30
ttxOr are they released at the same time with the same version numbers09:30
daemontool_I've followed the example from  https://github.com/openstack/releases/blob/master/doc/source/instructions.rst at the very end09:30
daemontool_we try to release them09:30
ttxAre they a single "thing" or two separate things09:30
daemontool_same time with same version numbers09:30
daemontool_they are two separate things09:30
daemontool_but released at the same time09:30
daemontool_for consistency09:30
daemontool_not sure is the best way09:30
ttxwould someone install one but not the other ?09:31
daemontool_it can happen09:31
daemontool_yes09:31
ttxOK, then you want two deliverables09:31
daemontool_ok09:31
ttxwhich means, two YAML files09:31
daemontool_so I'm going to make two separate commit?09:31
daemontool_ok09:31
ttxyes, two separate commits09:31
daemontool_I'm going that also right now09:31
ttxoh well, since you already tagged those09:31
ttxyou can submit a single patch09:32
ttxAlso next time, let us process them09:32
daemontool_so one commit, two UAML files09:32
daemontool_ok09:32
daemontool_thanks a lot ttx09:32
ttxand post the governance change and link to it09:33
ttxso that everything is aligned09:33
daemontool_ok09:33
daemontool_sure09:33
ttxIf you do it very quickly I'll include freezer in the mitaka-2 announcement09:33
ttxI'm writing it now09:33
daemontool_ok09:34
daemontool_doing it right now09:35
openstackgerritFausto Marzi proposed openstack/releases: openstack/freezer openstack/freezer-api 2.0.0.0b2 Mitaka 2  https://review.openstack.org/27107009:37
openstackgerritFausto Marzi proposed openstack/releases: openstack/freezer openstack/freezer-api 2.0.0.0b2 Mitaka 2  https://review.openstack.org/27107009:39
ttxdaemontool_: could you remove the strict depend-on ? I'd like to merge the releases part without waiting for the governance patch09:40
daemontool_ok09:40
ttxjust link to it without a depends-on09:40
openstackgerritFausto Marzi proposed openstack/releases: openstack/freezer openstack/freezer-api 2.0.0.0b2 Mitaka 2  https://review.openstack.org/27107009:41
ttxdaemontool_: last thing: could you push the tag for freezer-api 2.0.0.0b2 ?It has 2.0.0b2 right now09:43
ttxwhich will fail tarball generation09:43
daemontool_ah09:43
daemontool_ok09:43
ttxnext time we'll just process it09:43
ttxbut since you started this round...09:44
daemontool_ok09:44
daemontool_done09:44
daemontool_better I learn09:44
openstackgerritMerged openstack/releases: openstack/freezer openstack/freezer-api 2.0.0.0b2 Mitaka 2  https://review.openstack.org/27107009:49
ttxhrm, for some reason the freezer-api tag doesn't generate tarballs09:50
ttxinvestigating09:50
ttxdaemontool_: https://jenkins07.openstack.org/job/freezer-api-tarball/2/console09:54
ttxfeels like you are missing quite a few bits in freezer-api tox.ini09:54
ttxso no tarballs are generated there09:55
ttxI'll have to remove freezer from the releases pages09:55
ttxor at least freezer-api09:55
ttxdaemontool_: should I keep freezer if we can't include freezer-api yet ?09:56
daemontool_ok09:58
daemontool_yes09:59
daemontool_please09:59
ttxok09:59
daemontool_I think is because of the requirements10:00
daemontool_? https://review.openstack.org/#/c/271072/10:00
ttxoh maybe yes10:00
daemontool_anyway yes please do not be blocked by us10:00
daemontool_move forward as you think is better10:00
openstackgerritThierry Carrez proposed openstack/releases: Removing freezer-api entry  https://review.openstack.org/27120910:00
daemontool_ttx, classic question of the case:  can we include it for M3? : )10:02
ttxsure10:02
daemontool_ah great10:03
*** dtantsur|afk is now known as dtantsur10:06
openstackgerritMerged openstack/releases: Removing freezer-api entry  https://review.openstack.org/27120910:09
*** Qiming has quit IRC10:37
*** dims has joined #openstack-release11:00
*** Qiming has joined #openstack-release11:15
openstackgerritDmitry Tantsur proposed openstack/releases: Release ironic-inspector 3.0.0 for Mitaka  https://review.openstack.org/27011911:24
*** openstackgerrit has quit IRC11:47
*** openstackgerrit has joined #openstack-release11:47
*** openstackgerrit has quit IRC12:33
*** openstackgerrit has joined #openstack-release12:33
*** gordc has joined #openstack-release12:34
*** [1]Thelo has joined #openstack-release12:34
*** Thelo has quit IRC12:36
*** [1]Thelo is now known as Thelo12:36
openstackgerritQiming Teng proposed openstack/releases: Senlin mitaka-2 milestone  https://review.openstack.org/27127112:40
openstackgerritQiming Teng proposed openstack/releases: Senlin mitaka-2 milestone  https://review.openstack.org/27127112:40
dhellmannttx: good morning12:50
dhellmannttx: it looks like you picked up the last few stragglers, aside from senlin which appears to have been submitted a few minutes ago12:53
ttxyep12:54
ttxwe'll review status during the meeting12:54
* dhellmann nods and goes to find breakfast12:55
*** dims is now known as dimsum__13:00
*** daemontool_ has quit IRC13:04
*** dtantsur is now known as dtantsur|brb13:11
*** dtantsur|brb is now known as dtantsur13:42
*** doug-fish has joined #openstack-release13:55
bswartzttx, dhellmann: thanks, sorry for the extra work last night13:57
dhellmannbswartz : no problem13:57
*** mriedem has joined #openstack-release14:22
*** pcaruana has joined #openstack-release14:49
*** sigmavirus24_awa is now known as sigmavirus2415:13
dhellmanngordc: https://review.openstack.org/#/c/271366/15:14
gordcdhellmann: ack. let me check with core team (in case next ptl has opinion)15:14
dhellmanngordc : this is not really an optional correction for this cycle. you can change it at the start of the next cycle, but we need to communicate what is actually being done15:15
gordcdhellmann: i see. yeah, i'm fine with it then. i don't expect any random releases between now and m315:16
dhellmanngordc : cool, thanks, please +1 so ttx knows he can merge it next week15:16
gordcdone15:16
dhellmanngordc : thanks!15:20
odyssey4mewhere do the release notes published through reno get published?15:59
tonybodyssey4me: http://docs.openstack.org/releasenotes/openstack-ansible/16:14
odyssey4menever mind found it - http://docs.openstack.org/releasenotes/<project name>/16:14
odyssey4melol, thanks tonyb16:14
ttxdhellmann: should we still tag the 0b2 for senlin ?16:18
ttxI guess yes, since they could push it themselves anyway16:19
ttxhe just pushed a release model change16:20
*** Qiming has quit IRC16:22
dhellmannttx: yep, I'll do that after lunch17:05
*** dtantsur is now known as dtantsur|afk17:33
-openstackstatus- NOTICE: Restarting zuul due to a memory leak17:51
*** LouisF has joined #openstack-release18:12
LouisFdhellmann: i posted https://review.openstack.org/#/c/271015/1 to release networking-sfc to m218:13
LouisFcan you workflow+118:14
openstackgerritSergey Kraynev proposed openstack/releases: Release python-heatclient 0.9.0  https://review.openstack.org/27117318:47
*** gordc has quit IRC19:48
dhellmannLouisF : we're holding off on releasing things that get published to pypi until Monday, but we will process the request then19:56
*** dims has joined #openstack-release19:57
*** dimsum__ has quit IRC19:57
openstackgerritMerged openstack/releases: Senlin mitaka-2 milestone  https://review.openstack.org/27127120:05
*** pcaruana has quit IRC20:14
odyssey4medhellmann odd, I made reference to `foo: false` in a release note and the scanner barfed, resulting in the build failing (mapping values are not allowed here) - so I revised the note to not include that, but somehow it still has the old doc :/21:19
odyssey4meanyone seen anything like that?21:19
dhellmannodyssey4me : link?21:19
odyssey4medhellmann this is the original barf: http://logs.openstack.org/20/271520/1/check/gate-openstack-ansible-releasenotes/058d58d/21:20
odyssey4melemme upload my patched version and see if the gate barfs, or whether this is localised to my workstation21:20
*** LouisF has quit IRC21:34
dhellmannodyssey4me : you may have to commit the change for reno to pick it up locally21:37
dhellmannodyssey4me : reno only looks at the contents of files *in git* not in your working copy21:37
odyssey4medhellmann aha, I forgot about that - thanks :)21:38
odyssey4me<-- releasenotes noob21:38
dhellmannit's not an obvious thing, I forget myself sometimes :-)21:38
*** pcaruana has joined #openstack-release21:48
*** doug-fish has quit IRC21:49
*** mriedem has quit IRC21:51
*** gordc has joined #openstack-release22:01
openstackgerritgordon chung proposed openstack/releases: ceilometer 5.0.2 release - liberty  https://review.openstack.org/27090922:07
openstackgerritgordon chung proposed openstack/releases: ceilometer 5.0.2 release - liberty  https://review.openstack.org/27090922:32
*** [1]Thelo has joined #openstack-release22:35
*** gordc has quit IRC22:37
*** Thelo has quit IRC22:38
*** [1]Thelo is now known as Thelo22:38
openstackgerritDoug Hellmann proposed openstack/releases: rearrange content in preparation to move to new vhost  https://review.openstack.org/27155022:44
openstackgerritDoug Hellmann proposed openstack/releases: add newton and ocata pages  https://review.openstack.org/27155122:44
openstackgerritJohn Dickinson proposed openstack/releases: swift 2.6.0 release  https://review.openstack.org/27155522:50
*** dims_ has joined #openstack-release22:56
openstackgerritDoug Hellmann proposed openstack/releases: add newton and ocata pages  https://review.openstack.org/27155122:56
openstackgerritDoug Hellmann proposed openstack/releases: import some known EOL dates  https://review.openstack.org/27155822:56
*** dims has quit IRC22:58
*** sigmavirus24 is now known as sigmavirus24_awa23:00
*** dims_ has quit IRC23:13
*** dims has joined #openstack-release23:56

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