Friday, 2016-02-26

*** cody-somerville has quit IRC00:09
*** sdague has quit IRC00:26
*** devanand1 has joined #openstack-release00:59
*** devanand1 has quit IRC00:59
*** devananda has quit IRC00:59
*** devananda has joined #openstack-release01:01
*** devananda has quit IRC01:26
*** devananda has joined #openstack-release01:27
*** devananda has quit IRC01:27
*** devananda has joined #openstack-release01:30
*** dims has quit IRC01:49
*** david-lyle has quit IRC02:41
*** dims has joined #openstack-release03:10
openstackgerritDavanum Srinivas (dims) proposed openstack/releases: Final oslo.messaging release for Mitaka (4.5.0)  https://review.openstack.org/28509103:22
*** amotoki has joined #openstack-release03:41
*** amotoki has quit IRC04:05
*** amotoki has joined #openstack-release04:20
*** amotoki has quit IRC04:30
*** amotoki has joined #openstack-release04:35
*** amotoki has quit IRC05:00
*** amotoki has joined #openstack-release05:07
openstackgerritMerged openstack/releases: Final oslo.messaging release for Mitaka (4.5.0)  https://review.openstack.org/28509105:26
openstackgerritSteve Martinelli proposed openstack/releases: releae keystoneclient 2.3.0  https://review.openstack.org/28512506:24
*** dims has quit IRC06:37
*** cody-somerville has joined #openstack-release07:06
*** cody-somerville has quit IRC07:06
*** cody-somerville has joined #openstack-release07:06
*** cody-somerville has quit IRC07:46
*** nikhil has quit IRC09:04
openstackgerritMerged openstack/releases: check for retagging in validation  https://review.openstack.org/28486910:15
openstackgerritMerged openstack/releases: test first release candidate  https://review.openstack.org/28471310:15
ttxdhellmann: tested RC1 ok. Now we need to create stable/meiji, push an additional commit to it, and tag RC2 from there10:17
ttxwaiting for you since you said you wanted to run the stable branch creation script. Just let me know which command you end up running, for my files10:17
ttx(note: RC1 doesn't appear on releases.o.o because there was a race between the two releases publication postjobs)10:22
*** sdague has joined #openstack-release10:26
*** dtantsur|afk is now known as dtantsur10:30
openstackgerritMerged openstack/releases: update the list-changes output to make it easier to read  https://review.openstack.org/28430310:39
dhellmannttx: brewing tea, brb11:09
dhellmannttx: ok, we want "./make_stable_branch.sh meiji release-test 0.0.1.0rc1" but I'll wait for you before running it11:13
dhellmannttx: around?11:52
dhellmannttx: I'm going to go ahead and run the command to create the branch, so we can get the changes it submits into the check queue.12:08
openstackgerritDoug Hellmann proposed openstack/release-test: Update reno for stable/meiji  https://review.openstack.org/28526112:09
dhellmannhttps://review.openstack.org/285260 Update .gitreview for stable/meiji12:09
*** krotscheck_dcm is now known as krotscheck12:13
openstackgerritMerged openstack/release-test: Update reno for stable/meiji  https://review.openstack.org/28526112:15
openstackgerritDoug Hellmann proposed openstack/releases: test final release  https://review.openstack.org/28471512:20
openstackgerritDoug Hellmann proposed openstack/releases: test second release candidate  https://review.openstack.org/28471412:20
openstackgerritDoug Hellmann proposed openstack/releases: support tarball names that do not match the repository name  https://review.openstack.org/28487012:20
dhellmannttx: branch created, .gitreview updated, and rc1 release request updated to point to the new patch12:21
*** amotoki_ has joined #openstack-release12:32
*** amotoki has quit IRC12:34
dhellmannttx: the rc1 patch is ready for you to review and process. I'm going to find some breakfast, bbiab12:51
*** gordc has joined #openstack-release13:00
ttxyou mean rc2 ?13:23
ttxprocessing13:24
openstackgerritMerged openstack/releases: test second release candidate  https://review.openstack.org/28471413:27
ttxLGTM13:29
ttxtriggered recheck on the final. waiting for you before processing it13:30
dhellmannttx: oops, yes rc213:33
ttxNow the last question is, will the final trigger the announcement and the right changelog13:34
dhellmannttx: "right changelog"? in the announce email?13:35
dhellmannI don't think we've merged the change to reno to default to collapsing changes, and I don't think we're doing that explicitly in the release announcement13:35
dhellmannhttps://review.openstack.org/27876113:36
ttxhmm13:42
ttxDo we want an announcement email for every deliverable on the final, or a single one13:43
ttx(single one pointing to the releases.o.o/mitaka page)13:44
ttxdhellmann: Should I process the final and see ?13:44
dhellmannoh, we'll get an email if you process it13:45
dhellmannthe question is what will it contain :-)13:45
dhellmannttx: we don't differentiate now between libs and services for triggering the email13:45
dhellmannanything that looks like a final release gets an email, basically13:46
ttxOh well, I guess that's fine13:47
* ttx processes final13:47
dhellmannwe could set up different templates in zuul for the different release models, to not send email announcements13:47
ttxI don't think it's a bad thing to send out the list of changes at final release time. We do that on point releases already13:48
dhellmannyeah, that's what I thought when I set it up this way13:48
ttxwas just thinking out loud13:48
dhellmannthe thing is, the email is only going to include reno notes since the last rc13:48
dhellmannthat will change when we change the default in reno, though13:49
openstackgerritMerged openstack/releases: test final release  https://review.openstack.org/28471513:49
ttxdhellmann: One thing I noticed, but might be just due to release-test setup: it has meta:pypi yes13:54
*** dims has joined #openstack-release13:54
ttxI suspect the services would not have that set ?13:54
dhellmannttx: oh, right. I think the default is yes so we need to add the flag to turn that off13:54
dhellmannttx: we could fix that before you tag the release, if you haven't already13:55
dhellmannah, you have13:55
dhellmannno problem13:55
dhellmannthe default seems to be "no" in at least one place13:59
ttxhaven't got the email yet13:59
ttxquick biobreak before meeting14:00
dhellmannah, I see the logic error14:00
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: fix default handling for pypi link  https://review.openstack.org/28531114:01
dhellmannemail sending failed because relaying is not permitted: http://logs.openstack.org/c6/c69787906a44a8bc46ac7ef8f29f02274ec08851/release/release-test-announce-release/36b067c/console.html14:05
*** sdake has joined #openstack-release14:12
sdakehey folks14:12
sdakethinking of adopting reno for kolla14:12
sdakeI have one question14:12
sdakewhere is the version set in the release note?14:12
dhellmannsdake : the version is detected based on where the note is in the commit history of the project, and the tags the project has14:15
dhellmannsdake : we're in a meeting atm, but I can chat more at the top of the hour14:15
sdakesorry didnt realize14:15
sdakeok woudl appreciate it dhellmann14:15
*** sdake has quit IRC14:35
*** amotoki_ has quit IRC14:36
*** dansmith is now known as superdan14:36
*** kzaitsev_mb has joined #openstack-release14:42
kzaitsev_mbdhellmann: I actually had another question =) what does 'final release for clients' mean exactly? I mean, that I would probably still have permissions to release another OS client after it (not that I'm intending to)14:43
kzaitsev_mbso is it about the last chance to have requirements being updated in global-requirements?14:44
dhellmannkzaitsev_mb : we want you to release next week, and then not again until after the server projects have their releases finished unless there is a critical bug in the client14:44
dhellmannafter the server project stable branches are created, we'll resume releasing libs from master (clients and other)14:44
kzaitsev_mbok, I see. so next week should be literally last release for client.14:45
dhellmannuntil you start doing stable releases, yes14:45
kzaitsev_mbbut it would still be ok to accept commits to client's master, right?14:46
dhellmannkzaitsev_mb : yes, though you should be conservative about that in case you have to backport a change to the stable branch for a quick release during those few weeks14:47
kzaitsev_mbwouldn't it be logical to branch stable/mitaka for client repos next week then?14:48
kzaitsev_mb(just thinking out loud)14:48
*** amotoki has joined #openstack-release14:48
dhellmannkzaitsev_mb: you have until the end of the week to release, so we'll do the branch early the following week14:51
dhellmannwe will branch from a tagged release, so you shouldn't lose any dev time14:51
kzaitsev_mboh, great =)14:51
kzaitsev_mbok, so back to release procedure. How do I do it by the book for murano? because I'm following instructions, from my predecessor and they include tagging the commit manually (i.e with git tag command). https://wiki.openstack.org/wiki/ReleaseTeam/How_To_Release is this doc up to date?14:53
dhellmannok, some of that process is out of date14:54
dhellmannthere's a script in openstack-infra/release-tools called release.sh14:55
dhellmannI think you'll just want to run that script14:55
dhellmannit will update launchpad for you, so you'll need your launchpad credentials set up14:56
dhellmannyou can use the launchpad-login command in that repo14:56
dhellmannto run it, you'd run "tox -e venv -- launchpad-login"14:57
dhellmannhttp://git.openstack.org/cgit/openstack-infra/release-tools/tree/README.rst14:57
kzaitsev_mbI think I have them set up, since I've been using some of the scripts from release-tools to update l-pad milestones14:57
dhellmannok, good14:57
kzaitsev_mbthanks, I'll read through the script then14:58
dhellmannwe don't do anything with milestones any more in the scripts, so if you want to keep using them you will have to do that part by hand or use the older scripts14:58
dhellmannif you use release.sh it will set up your commit message with the metadata needed for the announcement email to work14:58
dhellmannkzaitsev_mb : you should also make sure to submit a patch to the releases repo to record your release tag, after you've applied it14:58
*** mriedem has joined #openstack-release14:58
*** amotoki has quit IRC15:02
*** sdake has joined #openstack-release15:05
*** sigmavirus24_awa is now known as sigmavirus2415:07
dhellmannsdake: I'm here if you still have questions15:08
sdakeI do but have rx appointment in 45 mins15:08
sdakeI should be back in a few hours15:08
dhellmannsdake : ok, I'll be around just ping me here or send email to the dev list tagged [release]15:08
sdakecan we chat then?  I'm really keen to get rolling with reno15:08
dhellmannyep, I'm happy to help you get set up15:09
sdakethe one question I Have is how do we backdate the release notes for history sake15:09
sdakeor do we justignore that, and only do it going forward?15:09
dhellmannsdake : what I've been recommending that folks do is edit the sphinx input files for older notes, if you want to do that15:10
dhellmannand then use reno for newer notes going forward15:10
sdakeok i've actually got to roll soon, but sphinx input editing sounds reasonable - an example would help :)15:10
sdakedoes reno convert the yaml to sphinx?15:11
dhellmannI'll see if I can find anyone who has done that, but it would be in a file like releasenotes/source/liberty.rst or older15:11
dhellmannsdake : yes15:11
dhellmannsdake : http://docs.openstack.org/developer/reno/15:11
sdakei did rtfm arleady :)15:12
sdakebit missed info about that15:12
dhellmannthe sphinx extension page should cover that, though maybe not explicitly15:12
sdakeok, i may need a little hand holding relating to older milestone releases, but i'll try to get all the rsts in reno format for mitaka-315:12
dhellmannsounds good, I can help with more specific answers when you have more time15:13
sdakeis reno smart enough to combine mitaka1/2/3 into the final mitaka release based uon the tag id?15:13
dhellmannyes, we have the patch for that up for review right now15:13
sdakenice15:13
dhellmannso by the time we tag final releases, it will be the default15:13
sdakei actually have a heat blueprint for kolla to finish the job on first, then i'll sort out reno prior to the 2nd-4th :)15:14
sdakewhich is our tagging window for mitaka315:14
dhellmannyep, that's next week15:15
*** kzaitsev_mb has quit IRC15:15
openstackgerritMerged openstack/releases: releae keystoneclient 2.3.0  https://review.openstack.org/28512515:15
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: fix default handling for pypi link  https://review.openstack.org/28531115:16
sdakeyup but we have all the data already dhellmann so shoudl be easy as long as adding reno to a repo isn't terribly difficult15:25
*** nikhil has joined #openstack-release15:25
dhellmannsdake : just a couple of patches to set it up in the repo and turn on the jobs in CI15:25
sdakewhich type of jobs?15:26
dhellmannsdake : some example patches: https://review.openstack.org/#/q/topic:add-reno,n,z15:26
dhellmannyou need the job to actually build the published notes15:26
sdakedhellmann isn't that just part of doc job, or a separate job?15:27
*** kzaitsev_mb has joined #openstack-release15:27
dhellmannsdake : separate job because they go to a different url15:27
sdakegot it, well I understand project-config pretty well15:27
sdakeso that should be easymode15:27
dhellmannsdake : the original instructions are in http://lists.openstack.org/pipermail/openstack-dev/2015-November/078301.html15:28
sdakewish I was aware of this months ago15:28
sdakehard to stay on top of regular openstack-dev15:28
sdakeneed to filter release i htink ;)15:28
dhellmannthough I think at that point I missed the need for the "unreleased" page for testing15:28
dhellmannsdake : all the best release liaisons and ptls do ;-)15:28
sdakedhellmann thanks :)15:29
sdakedhellmann well I'm far from perfect, had medical problem (root infection in tooth) in nov/dec15:29
sdakeso missed alot of what happened during that period unforutnately15:30
dhellmannsdake : sure, I'm just teasing, I remember you said you had some medical issues a while back15:30
dhellmannsdake : when you're ready to go, let me know and I'll help you get set up15:31
sdakeya two root canals back to back15:31
sdakeone failed15:31
sdakesucked ass :(15:31
dhellmannouch :-(15:31
sdakecool, likely monday or this weekend some time ;)15:31
sdakeon the plus side the docs gave my oxycodone 5mg so I was pretty much out to lunch for about a month :)15:31
dhellmannthat's a long time to be hazy :-)15:32
sdakeyour telling me15:32
sdakeok gotta roll15:32
dhellmanndrop a note here with the patch link if you do the work this weekend, otherwise I'll see you monday15:32
*** sdake has quit IRC15:47
*** mriedem has quit IRC15:49
*** mriedem has joined #openstack-release15:53
*** mriedem is now known as mriedem_meeting15:54
openstackgerritSergey Kraynev proposed openstack/releases: Release python-heatclient-1.0.0  https://review.openstack.org/28385216:08
*** mriedem_meeting has quit IRC16:08
*** mriedem has joined #openstack-release16:14
*** mriedem has left #openstack-release16:18
*** mriedem has joined #openstack-release16:18
notmynamedhellmann: so what if a project isn't using reno for release notes? how do their end-of-cycle notes get included? (re your ML post)16:21
*** dims has quit IRC16:22
dhellmannnotmyname : you can put a link to the notes in your deliverables file in the releases repository16:22
dhellmannnotmyname : the other projects will, when they have mitaka pages to link to, do the same thing to their reno-generated notes16:23
notmynamedeliverables file? is that MANIFEST.in?16:23
dhellmannnotmyname : in the openstack/releases repo where you request tags16:23
dhellmanndeliverables/mitaka/swift.yaml16:23
notmynameah, ok16:23
notmynamewhat do you mean by link to it? with reno, is there an artifact produced and hosted somewhere that's linked to?16:24
notmynameor is it refering to an in-tree file?16:24
dhellmannnotmyname : yes http://docs.openstack.org/releasenotes/keystone/16:25
notmynameto the first or second thing?16:25
dhellmannprojects using reno have their published notes updated at a site like ^^ automatically every time they merge a commit or tag a release16:25
dhellmannwe will put a link to those pages in their deliverables file, to cause them to be linked from the right page on releases.openstack.org16:26
dhellmannfor example, we have links associated with several projects for liberty on http://releases.openstack.org/liberty/index.html16:26
dhellmannso if you want to publish your notes somewhere else, you can just provide a link to wherever they end up16:26
notmynamethanks for the info16:30
openstackgerritSergey Kraynev proposed openstack/releases: Release python-heatclient-1.0.0  https://review.openstack.org/28385216:56
*** dims has joined #openstack-release17:09
*** dims has quit IRC17:10
*** bknudson_ has joined #openstack-release17:12
*** pleia2_ has joined #openstack-release17:15
*** tonyb_ has joined #openstack-release17:16
*** coreycb` has joined #openstack-release17:18
*** stevebak` has joined #openstack-release17:19
*** krotscheck has quit IRC17:20
*** bknudson has quit IRC17:20
*** notmyname has quit IRC17:20
*** onovy has quit IRC17:20
*** tonyb has quit IRC17:20
*** bswartz has quit IRC17:20
*** coreycb has quit IRC17:20
*** pleia2 has quit IRC17:20
*** stevebaker has quit IRC17:20
*** peterstac has quit IRC17:20
*** krotscheck has joined #openstack-release17:20
*** onovy_ has joined #openstack-release17:20
*** onovy_ is now known as onovy17:21
*** notmyname has joined #openstack-release17:21
*** peterstac has joined #openstack-release17:21
*** dims has joined #openstack-release17:22
flaper87dhellmann: How bad would it be for us to release a glance_store version on Monday given this is the non client libs freeze week?17:32
flaper87We could do a release today17:33
flaper87but I'd rather not do that on Fridays and, unfortunately, there's still one patch going through the gate17:33
*** sdake has joined #openstack-release17:34
dhellmannflaper87 : not the end of the world, but not great. how many projects are using it now?17:35
flaper87dhellmann: known by us, just Glance, which is why I wasn't too worried about requesting this17:36
dhellmannflaper87 : I can confirm that looking at the existing requirements files17:37
dhellmannflaper87 : ok, let's do it monday as early as possible17:37
flaper87dhellmann: ok, I'll ask EU folks to take care of it17:39
flaper87dhellmann: thank you17:39
dimsttx : please bless https://review.openstack.org/#/c/285400/17:49
dimshmm, no patchbot :)17:49
notmynamedo you want patchbot here?17:49
dimsnotmyname yes please :)17:49
*** dtantsur is now known as dtantsur|afk17:49
*** patchbot has joined #openstack-release17:49
notmynamepatchbot: hello17:49
dimsthanks notmyname17:50
*** dims is now known as dimsum__18:09
*** kzaitsev_mb has quit IRC18:09
openstackgerritDoug Hellmann proposed openstack/releases: remove meiji test files  https://review.openstack.org/28548118:14
*** mriedem has quit IRC18:18
openstackgerritDoug Hellmann proposed openstack/releases: support tarball names that do not match the repository name  https://review.openstack.org/28487018:53
openstackgerritDoug Hellmann proposed openstack/releases: collapse pre-releases into final releases  https://review.openstack.org/28549718:53
openstackgerritDoug Hellmann proposed openstack/releases: remove meiji test data  https://review.openstack.org/28549818:53
*** bswartz has joined #openstack-release18:55
*** sdague has quit IRC19:06
*** dimsum__ has quit IRC19:16
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: better handling of stable flag  https://review.openstack.org/28552019:47
*** gordc has quit IRC19:51
*** sdague has joined #openstack-release20:13
*** yarkot_ has joined #openstack-release20:22
*** gordc has joined #openstack-release20:23
*** yarkot_ has quit IRC20:26
mordreddhellmann, ttx: https://review.openstack.org/#/c/285529/20:37
patchbotmordred: patch 285529 - openstack - Trim entries from submodules file that don't exist20:37
dhellmannmordred : those are "not really part of openstack" things, I guess?20:38
mordreddhellmann: well, they  don't actually have submodules in the repo20:39
mordreddhellmann: they're just vestigal entries in the .gitmodules file20:39
dhellmannah20:39
mordreddhellmann: (I noticed this as the result of a script I was running for a completely different purpose :) )20:40
dhellmannI'm not sure what the difference is between submodules and .gitmodules, since I've never used the feature20:40
dhellmannit doesn't matter though, I'll give you the benefit of the doubt ;-)20:40
mordred:)20:40
dhellmannI'm going to call it a day, have a good weekend!20:42
mordreddhellmann: same to you!20:42
*** dims has joined #openstack-release20:48
*** fesp has joined #openstack-release20:58
*** yarkot_ has joined #openstack-release21:13
*** yarkot_ has quit IRC21:29
*** fesp has quit IRC21:37
*** fesp has joined #openstack-release21:38
*** nikhil has quit IRC21:39
*** nikhil has joined #openstack-release21:57
*** gordc has quit IRC22:56
*** fesp has quit IRC22:59
*** dims has quit IRC23:07
*** sigmavirus24 is now known as sigmavirus24_awa23:08
*** dims has joined #openstack-release23:34
*** sdake has quit IRC23:53
*** sdake_ has joined #openstack-release23:53

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