Tuesday, 2015-11-24

*** openstackgerrit has quit IRC00:16
*** openstackgerrit has joined #openstack-release00:17
*** jhesketh has joined #openstack-release01:15
*** jhesketh has quit IRC01:16
openstackgerritKirill Zaitsev proposed openstack/releases: Update murano deliverables with 1.0.1 version  https://review.openstack.org/24896901:29
*** jgriffith_away is now known as jgriffith01:30
kzaitsev_mbok, I think th reason it was not included — was that we tagged 1.0.0 incorrectly =/ So probably this caused some confustion.01:31
kzaitsev_mbWonder if I should remove 1.0.0 (I believe I shouldn't) or somehow mark, that it was incorrectly tagged and should not be used.01:32
*** kzaitsev_mb has quit IRC01:45
*** bswartz has joined #openstack-release01:52
*** kzaitsev_mb has joined #openstack-release01:56
*** jhesketh has joined #openstack-release01:58
*** jhesketh has quit IRC02:03
*** jhesketh has joined #openstack-release02:06
*** amotoki has joined #openstack-release02:13
*** kzaitsev_mb has quit IRC02:15
*** david-ly_ has quit IRC02:36
*** dims has joined #openstack-release02:40
dimstonyb : can you please fix this merge conflict? https://review.openstack.org/#/c/248530/02:41
tonybdims: sure.02:43
openstackgerritTony Breeds proposed openstack/releases: Add a warning for new mitaka releases of oslo.messaging  https://review.openstack.org/24853002:51
dimsthanks tonyb +2A02:52
tonybdims: this time without addind EOF to the file ;p02:52
dimstonyb even better :)03:12
tonybdims: vim does it by default can't work out how to turn it off :(  I can use git add -p to work around it03:13
*** dims has quit IRC03:17
*** dims has joined #openstack-release03:22
*** dims has quit IRC03:35
*** david-lyle has joined #openstack-release04:08
*** aukhan has joined #openstack-release05:51
*** ifat_afek has joined #openstack-release07:05
*** jgriffith is now known as jgriffith_away07:15
openstackgerritMerged openstack/reno: force the right return type for mocked urandom  https://review.openstack.org/24658308:06
*** bdemers has quit IRC08:12
*** bdemers has joined #openstack-release08:14
*** ifat_afek has quit IRC09:06
*** mattoliverau has quit IRC09:10
*** matt6434 has joined #openstack-release09:11
*** openstackgerrit has quit IRC09:16
*** dtantsur|afk is now known as dtantsur09:17
*** openstackgerrit has joined #openstack-release09:17
*** ifat_afek has joined #openstack-release09:46
*** kzaitsev_mb has joined #openstack-release10:20
*** prometheanfire has quit IRC10:27
*** prometheanfire has joined #openstack-release10:29
openstackgerritMerged openstack/reno: add verbose and quiet options to command line for debugging  https://review.openstack.org/24658210:43
openstackgerritMerged openstack/reno: scan all changes and filter on files in reno not git log  https://review.openstack.org/24658410:43
*** aukhan has quit IRC10:48
*** dtantsur is now known as dtantsur|brb10:50
*** matt6434 has quit IRC10:54
*** matt6434 has joined #openstack-release10:55
*** bswartz has quit IRC10:56
*** bswartz has joined #openstack-release11:00
*** amotoki has quit IRC11:01
*** kzaitsev_mb has quit IRC11:01
*** dims has joined #openstack-release11:06
*** kzaitsev_mb has joined #openstack-release11:22
*** dtantsur|brb is now known as dtantsur11:51
*** bdemers has quit IRC12:55
*** gordc has joined #openstack-release12:59
*** jhesketh has quit IRC13:06
*** jhesketh has joined #openstack-release13:07
*** josh6627 has joined #openstack-release13:29
*** josh6627 has quit IRC13:29
*** doug-fish has joined #openstack-release13:30
*** jhesketh has quit IRC13:30
*** jhesketh has joined #openstack-release14:02
*** jhesketh has quit IRC14:03
*** ifat_afek_ has joined #openstack-release14:03
*** jhesketh has joined #openstack-release14:04
*** ifat_afek has quit IRC14:05
*** ifat_afek has joined #openstack-release14:09
*** ifat_afek_ has quit IRC14:12
openstackgerritGraham Hayes proposed openstack/reno: Add deprecations section to release notes  https://review.openstack.org/24770414:27
ttxoops14:28
mugsie?14:29
ttxdhellmann, dims: I just accidentally pushed a 3.0.1 tag for oslo.rootwrap, during new release tooling testing14:31
dimsttx gerrit master tip?14:31
ttxyeah, over 3.0.014:31
ttxI can kill it really fast14:31
dimsshould be fine14:31
ttxor just let it live14:31
*** amotoki has joined #openstack-release14:32
dimshttps://github.com/openstack/oslo.rootwrap/compare/3.0.0...3.0.114:32
dimsseems identical14:32
ttxyeah, same commit14:32
dimsno worries14:32
dimswe should be ok14:32
*** mriedem_away is now known as mriedem14:33
openstackgerritThierry Carrez proposed openstack-infra/release-tools: New tooling for service releases  https://review.openstack.org/24924114:37
openstackgerritThierry Carrez proposed openstack-infra/release-tools: [WIP] New tooling for service releases  https://review.openstack.org/24924114:38
ttxThis is the thing I was testing ^14:38
ttxdhellmann: still WIP ^ ping me when around to discuss what we actually want there14:39
dhellmannttx: at least you didn't accidentally send like 100 emails about it #beenthere14:42
dhellmannttx: do you think we'll be able to use release.sh for libraries, too? or do we need to make release_from_yaml.py decide whether to call that or release_postversion.sh for libs?14:43
ttxdhellmann: so that approach I took is taking release_postversion and strip it from the Launchpaddy things14:43
ttxand remove the release notes stuff since we may want to evolve that14:44
dhellmannok, that's what I expected but your commit message called out service projects14:44
dhellmannah, yeah, we need to decide what to do there. I think we still want release notes for libs to announce the new release14:44
ttxIdeally we would have a single thing that we could plug behind the tag jobs14:44
dhellmannexactly14:44
ttxTo simplify the discussion let's discuss what we want to do at mitaka-114:44
ttxWe said a number of things, I want to make sure we are on the same line14:45
dhellmann++14:45
ttxFor mitaka-1 we'll tag 13.0.0.0b1 things14:45
ttxwe said those would be requested through openstack/releases changes14:45
ttxbut that we would somehow not make thoise appear on docs.o.o/releases14:46
ttxsince they are technically not releases14:46
ttxCurrently the release.sh script does not distinguish14:46
ttxbetween milestones and real releases14:46
ttxthe only place where I considered detecting that was on the tag message14:47
dhellmannwe said that d.o.o/releases would only show pre-releases if those were the most recent release14:47
ttxdhellmann: oh right, that14:47
dhellmannso that work will all be done inside the releases repo, and it can wait until after the milestone14:47
*** jgriffith_away is now known as jgriffith14:47
*** kzaitsev_mb has quit IRC14:47
ttxSo the tag is pushed, that generates a tarball, the script actually doesn't wait for that14:47
ttxwe should probably watch for tarball job failure instead of having the script wait14:48
dhellmannwe used to wait for the tarball so we could download it and upload it to launchpad, right?14:48
ttxyes14:48
dhellmannok. we may not need it for m1, but at some point we need to upload signatures to the tarballs server, right? is the thing building the tarball going to do that step?14:48
ttxthen the script just posts messages on Launchpad bugs that happen to be mentioned between the last two tags14:49
ttxdhellmann: I suspect the automation will do all that ?14:49
dhellmannthat would make more sense14:49
ttxsince it will sign it can upload the signature14:49
ttxwe already trust the bot at that stage14:49
*** bdemers has joined #openstack-release14:49
dhellmannright14:50
ttxbut yeah, there is a part of the automation that will be triggered by the openstack/releases merge (basically what the release.sh script does)14:50
ttxand another that will be triggered by the tag push14:50
dhellmannok, the script is good for services, but we need to decide where we're going to send the release note email -- maybe that's a separate job or a separate publisher for library releases?14:50
ttx(tarball generation and upload)14:50
dhellmannright14:51
ttxThat leaves us with announcement, yes14:51
ttxWhat do we want to do there ?14:51
dhellmannI'm personally fine with including those emails for services as well as libraries, but that's not what we've done in the past14:51
ttxWe have 3 types of announcements now14:52
ttxManual ones like we did for liberty-314:52
ttx"We are thrilled to announce" type emails like we do for libs14:53
ttxand something we could build on top of reno14:53
dhellmannyeah, it would be interesting to see if we could convert the lib announcements to reno, too14:53
ttxdo we need to keep "We are thrilled to announce" type emails if we start using reno ?14:54
dhellmannalthough one aspect of the existing announcements reno wouldn't give us is the requirements change14:54
ttxsounds like release announcements could just parrot the reno content ?14:54
dhellmannI would prefer to have 1 system for those emails. If we think reno can do it, we don't need all of what we have now14:54
dhellmannright14:54
dhellmannreno already has a way to produce the report for a given version as restructuredtext to the console, and rst2txt will format that nicely as the body of an email, so it won't be hard14:55
dhellmannthe trick is that so far mostly services and not libs have adopted reno14:55
ttxso we might need a tool that builds the release announcement email for us to send after the fact, as a third step14:55
ttxuntil that can be rolled in the post-tag automation with the rest14:55
dhellmannthat sounds right14:56
dhellmannI'll think about that some today14:56
ttxOne grey area: the signatures -- should we do anything about that between now that we drop LP and when we'll have teh upload automation/signing set up ?14:56
dhellmannmaybe that's something to build into reno itself, with a thin wrapper to pass it some arguments14:56
dhellmannwe should talk to fungi about the signing part -- I haven't had a chance to catch up with him about my spec, yet, either. Maybe we can grab him today.14:57
stevemarttx: thanks for replying to my questions on ML14:57
ttxSo ideally we would build two new scripts. One to run on when the openstack/releases change is merged, ultimately to run as post-merge hook on that repo (let's call that one release.sh) and one to run when the tarball is built, ultimately to run as part of the tarball creation/upload job (let's call that one tarball.sh)14:59
*** kzaitsev_mb has joined #openstack-release14:59
ttxrelease.sh needs to push the tag and add mentions to the LP bugs14:59
ttxtarball.sh needs to generate signature and upload it and prepare release announcement15:00
ttxwe may want to skip on the sig right now15:00
dhellmannrather than writing a new tarball.sh, we could also just add some steps to the existing script that is building the tarballs in the first place15:00
ttxsure, that would likely be in the same script in the end. But for mitaka-1 we might want it as a standalone tool to run manually15:01
fungii do have a spec for hosting the tarball signatures, and also uploading them to pypi15:01
dhellmannttx: sure15:01
ttxI'm just double-checking we need two tools/jobs. I think we do15:01
dhellmannfungi : that's right, I keep forgetting that's a separate spec15:02
ttxsince those are about two separate repos15:02
dhellmannttx: right15:02
fungithe tarball/wheel signing will happen on a trusted worker as an intermediate step between building the tarball and uploading it to pypi15:02
ttxIf we agree, release.sh as I just proposed it is probably not very far of what we need for the first script.15:03
dhellmannfungi : we also want signatures for things not uploaded to pypi15:03
dhellmannttx: yep, modulo the one comment I left about that read call15:03
ttxI'd say it should be even less aggressive validating input (that should run as an openstack/releases check job instead)15:03
dhellmannI think I agree with that15:04
dhellmannit should be safe to have it run with a tag that already exists, for example15:04
fungi1. normal worker builds tarball/wheel and stores them on tarballs.o.o, 2. signing worker retrieves tarball/wheel and generates signatures which are then stored adjacent to them on tarballs.o.o, 3. upload worker retrieves tarball/wheel/signatures and validates them before uploading to pypi/maven central/npm/wherever15:04
ttxAre you fine working on the other script ? The "let's prepare a release announcement" one to run as part of the tarball automation15:04
dhellmannfungi : ok, I was worried about part of step 2 there and it sounds like that's covered15:05
fungiyeah, we'll host our own copies of the signatures15:05
dhellmannttx: yeah, I'll work on an announce.sh15:05
fungii've also set tarballs.o.o working via https since a few weeks ago15:05
dhellmannfungi : ok, good15:05
dhellmannooh, I should update the releases repo links if they aren't already https15:05
ttxdhellmann: detecting that the Launchpad messages were already pushed would be a bit unreliable though. So the script would just repost the message15:05
ttxharmless, but not idempotent :)15:06
dhellmannyeah, I agree there15:06
fungianyway, i'm hoping to get started on the signing work in the next few weeks, emergencies permitting15:06
dhellmannfungi : have you had a chance to review https://review.openstack.org/#/c/245907/ ?15:06
ttxdhellmann: I'll rewrite the tool so that it takes YAML as input15:07
ttx(release.sh)15:07
dhellmannfungi : feel like it's probably incomplete15:07
fungilikely not, i was out of town with no internet access for the past week+15:07
fungilooking now15:07
dhellmannttx: nah, we'll have release_from_yaml.py call release.sh15:07
ttxdhellmann: ah, ok15:07
dhellmannttx: that way release_from_yaml can make multiple calls to it, and release.sh only needs to deal with one set of inputs15:07
dhellmannfungi : yeah, I thought probably  not15:07
fungiyeah, looks like you uploaded that after i went on vacation15:07
fungii'll stick it on my priority pile15:08
dhellmannttx: do you want to update release_from_yaml.py, too?15:08
dhellmannfungi : thanks!15:08
*** dims_ has joined #openstack-release15:08
ttxdhellmann: I'll look into it yes15:08
dhellmannok, thanks15:09
*** dims has quit IRC15:09
dhellmannI'll talk with dims about getting oslo converted over to use reno15:09
dhellmannI should probably make a more general announcement that we will want to use reno for release note emails for all projects, including libs15:10
*** kzaitsev_mb has quit IRC15:10
dhellmannttx: since the libraries are developer-focused, what do you think about including the release notes in their regular documentation?15:15
ttxdhellmann: let's call the second script announce.sh and have a corresponding  announce_from_yaml.py ?15:16
dhellmanninstead of under d.o.o/releasenotes15:16
ttxdhellmann: sounds good15:16
* ttx is about to gut release_from_yaml from announcy stuff15:16
dhellmannttx: sure, or a mode flag on release_from_yaml.py15:16
dhellmannk15:16
* dhellmann ducks out briefly for some pre-holiday errands15:18
openstackgerritThierry Carrez proposed openstack-infra/release-tools: Release tagging automation  https://review.openstack.org/24924115:40
*** dims_ has quit IRC16:30
* dhellmann returns16:37
*** dims has joined #openstack-release16:46
dhellmannttx: if you'll approve https://review.openstack.org/#/c/248861/ I'll cut a reno release today16:49
*** bnemec has quit IRC16:50
ttxdhellmann: on it17:00
ttxdone17:01
* ttx runs to doctors appointment17:01
dhellmannttx: ty17:02
openstackgerritMerged openstack/reno: add complex formatting example  https://review.openstack.org/24886117:03
openstackgerritDoug Hellmann proposed openstack/releases: reno 1.1.0  https://review.openstack.org/24933217:13
*** dims has quit IRC17:18
*** dims_ has joined #openstack-release17:18
*** david-ly_ has joined #openstack-release17:19
*** david-l__ has joined #openstack-release17:23
*** david-ly_ has quit IRC17:23
*** david-lyle has quit IRC17:23
*** dtantsur is now known as dtantsur|afk17:28
*** david-l__ has quit IRC17:30
*** david-lyle has joined #openstack-release17:44
*** david-lyle has quit IRC18:03
*** david-lyle has joined #openstack-release18:11
*** mriedem has quit IRC18:17
*** ifat_afek has quit IRC18:20
*** mriedem has joined #openstack-release18:21
*** kzaitsev_mb has joined #openstack-release18:41
kzaitsev_mbsomeone said murano here. =)18:41
kzaitsev_mboh no. it was on infra, sotrry18:42
*** bnemec has joined #openstack-release18:47
openstackgerritDavanum Srinivas (dims) proposed openstack/releases: New release for pylockfile  https://review.openstack.org/24938519:11
openstackgerritDavanum Srinivas (dims) proposed openstack/releases: New release for pylockfile  https://review.openstack.org/24938519:14
*** kzaitsev_mb has quit IRC19:20
dims_kzaitsev_ws : murano19:21
openstackgerritMerged openstack/releases: keystonemiddleware 2.3.2 (liberty)  https://review.openstack.org/24892619:23
dims_dhellmann : switched to using the .1 release for the pylockfile ^^19:24
dhellmanndims_ : ack, just a sec19:24
dims_no hurries19:24
*** kzaitsev_mb has joined #openstack-release19:30
dhellmannlifeless : I'm going to be writing up instructions for liaisons to remove the version line from all setup.cfg files as part of the M1 tagging process. I want to confirm with you that I'm giving the instructions in the right order, which is that we should tag, and then remove the version line. I'm basing that on this experiment: http://paste.openstack.org/show/479801/ Does that match what you would expect?19:30
kzaitsev_mbyeah, dims_ it works like that =) I get a push notififcation when someone mentions me or the m word =) But right now I have terrible connectivity problems. (sorry for off-topic =))19:31
dims_haha, yes i do the same for oslo as well :)19:32
openstackgerritMerged openstack/releases: reno 1.1.0  https://review.openstack.org/24933219:32
lifelessdhellmann: yes19:33
lifelessdhellmann: that is what I'd expect19:33
dhellmannlifeless : perfect, thank you19:34
lifelessdhellmann: we should document this in the pbr docs19:34
dhellmannlifeless : indeed, I'll make a note to do that19:34
*** kzaitsev_mb has quit IRC19:36
*** kzaitsev_mb has joined #openstack-release19:41
*** kzaitsev_mb has quit IRC19:50
*** kzaitsev_mb has joined #openstack-release19:52
*** dims has joined #openstack-release19:53
*** dims_ has quit IRC19:56
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: move add_comment.py to a console script  https://review.openstack.org/24939619:58
*** bdemers has quit IRC20:04
*** bdemers has joined #openstack-release20:05
*** matt6434 is now known as mattoliverau20:52
openstackgerritMerged openstack/releases: Add a warning for new mitaka releases of oslo.messaging  https://review.openstack.org/24853020:53
*** kzaitsev_mb has quit IRC21:10
*** kzaitsev_mb has joined #openstack-release21:13
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: remove debug statement in release_from_yaml.py  https://review.openstack.org/24942621:21
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: fix error handling and bug reporting in release script  https://review.openstack.org/24942721:21
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: make release_from_yaml.py figure out the deliverable files for us  https://review.openstack.org/24942821:21
*** kzaitsev_mb has quit IRC21:21
dhellmannttx: next I'll refactor release_from_yaml.sh to support releasing and announcing ^^21:22
*** dims has quit IRC21:37
*** dims has joined #openstack-release21:38
*** gordc has quit IRC21:45
*** bdemers has quit IRC22:10
*** kzaitsev_mb has joined #openstack-release22:21
*** kzaitsev_mb has quit IRC22:26
*** mriedem has quit IRC22:38
*** doug-fis_ has joined #openstack-release22:49
*** doug-fish has quit IRC22:53
*** doug-fis_ has quit IRC22:53
*** mestery has quit IRC23:04
*** doug-fish has joined #openstack-release23:04
*** mestery has joined #openstack-release23:05
*** doug-fish has quit IRC23:08
*** dims_ has joined #openstack-release23:28
*** dims has quit IRC23:29

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