Tuesday, 2015-08-18

*** dims has joined #openstack-relmgr-office00:34
*** sigmavirus24 is now known as sigmavirus24_awa00:49
*** dims has quit IRC02:30
*** mestery has joined #openstack-relmgr-office04:59
*** mestery has quit IRC05:09
*** dims has joined #openstack-relmgr-office05:20
*** dims has quit IRC05:26
*** openstackgerrit_ has joined #openstack-relmgr-office06:43
ttxgordc: there is also the possibility to publish the existing file on PyPI.07:03
*** dims has joined #openstack-relmgr-office07:48
*** dims has quit IRC07:53
ttxI'm around for office hours by the way08:35
ttxtime for coffee I guess08:35
*** dims has joined #openstack-relmgr-office10:51
*** dims_ has joined #openstack-relmgr-office11:28
*** dims has quit IRC11:30
*** dims has joined #openstack-relmgr-office12:00
*** dims has quit IRC12:00
*** dims_ has quit IRC12:00
*** dims has joined #openstack-relmgr-office12:15
*** dims_ has joined #openstack-relmgr-office12:41
*** dims has quit IRC12:41
ttxdhellmann: ping me when you have some time for sync12:59
*** dims has joined #openstack-relmgr-office13:01
*** dims_ has quit IRC13:02
*** dims_ has joined #openstack-relmgr-office13:15
*** dims has quit IRC13:17
*** dims_ has quit IRC13:31
*** dims has joined #openstack-relmgr-office13:31
*** dims has quit IRC13:40
*** dims has joined #openstack-relmgr-office13:43
*** dims has quit IRC14:04
*** dims has joined #openstack-relmgr-office14:05
*** sigmavirus24_awa is now known as sigmavirus2414:11
dhellmannttx: here now, if you're around14:20
*** wshao has joined #openstack-relmgr-office14:30
ttxdhellmann: o/14:34
dhellmannttx: o/14:35
ttxbeen updating the etherpad at https://etherpad.openstack.org/p/liberty-release-mgmt14:35
*** dims_ has joined #openstack-relmgr-office14:35
ttxLet's quickly go through the list14:36
ttxRelease status tracking is a bit on hold due to more pressing matters14:36
ttxand we coevred all the mandatory things there14:36
ttxNew milestone / Intermediary release process14:36
ttxI think the only mandatory thing left there is the series mapping tool14:37
*** dims has quit IRC14:37
ttxtrying to prioritize a bit :)14:37
dhellmannyeah, I was going to do that with a sphinx extension14:37
dhellmannwhile you were out I made some good progress on rewriting release_postversion.sh in python, but there's still some work to make it do the launchpad parts and then handle multiple repositories14:37
dhellmannmaybe I should set that aside and work on the sphinx stuff?14:37
ttxno, I think we are still on track14:38
ttxjust trying to get to a priority for the last two months14:38
ttxpriority list14:38
dhellmannk14:38
ttxAutomating release process14:38
ttxI think we coeverd the minimum there too14:39
ttxand I can't type "coeverd"14:39
dhellmannI haven't started doing anything for automating pre-versioned releases based on the yaml files, but we can do those by hand like we did the milestones14:39
ttxright. Same status for Library release management14:39
ttx"Refining release models taxonomy and adjust tags accordingly"14:39
ttxI think we have a couple of "must do" there14:40
ttxsince starting with liberty release changing tags will get a bit more costly with people starting to use them14:40
ttxI had a few questions for you there14:40
ttxShould "Managed" be a team-level tag ?14:40
ttx(I should probably look at the diff)14:41
dhellmannI think not14:41
dhellmannneutron has a bunch of repositories for plugins that they don't want managed14:41
dhellmannand there are enough of them that I don't think we want to default to taking them on14:42
ttxok.14:42
dhellmannI think we should encourage teams to have a very good reason for having it be split, but we should not assume managed14:42
ttxSo the big work is to go through all teams and adjust the tags14:42
dhellmann(that's contrary to what I thought a few weeks ago until I fully understood the neutron situation, fwiw)14:42
ttxwe may want to rename  cycle-with-milestones to once-per-cycle before we do that14:42
ttxsince renames are a bit painful14:43
ttxhmm, in fact not really less painful to rename after14:43
dhellmannthat makes sense14:43
dhellmannheh14:43
ttxanyway, we'll probably have to engage with teams and propose per-team updates of the release: tags14:43
ttxsince trying to get them all in at the same time is quite a daunting rebase task14:44
ttxand then we should start being pickier about additions14:44
dhellmann++14:45
ttxso basically, split https://review.openstack.org/#/c/201724/14:45
ttxbut maybe engage with each team as we do so14:45
ttxprobably simpler to split the task14:45
dhellmannright, that was a stab at getting everyone to chime in, but I agree that splitting it will make it easier to land14:46
ttxStable branch tags can wait a bit14:46
ttxStable branches point releases release, not so much14:46
ttxcan you attend the cross-project meeting later today ?14:47
dhellmannI'm going to try14:47
ttxI'd like a clear way forward and a few people committed to make it happen14:47
ttxsince the "stable team" is not really staffed to make that transition happen, imho14:47
ttxIf I didn't push it it would still be ignored14:48
dhellmanncan you refresh my memory on the options there? IIRC it was do not tag; tag automatically on a merge; submit a release request patch automatically on a merge; and submit a release request patch automatically if there are changes within some period of time14:48
ttxthere are two topics, the versioning and the release notes generation14:48
ttxon the versioning front14:48
ttxyour options make sense14:49
ttxadditional option is on-demand only14:49
dhellmannoh, another option was to make pbr generate real versions instead of dev versions14:49
dhellmannI think that's a prereq for the "not tagging at all any more" option14:49
dhellmannah, right, so we have 5 options14:49
ttxyeah, but that option is not very popular (since pbr would generate duplicate versions on private branches)14:50
dhellmannand the release notes question we had talked about either using commit message tags or checking in notes as part of the cherry-pick14:50
dhellmannright14:50
ttxThe release notes discussion just evolved another +1 for taggign through openstack/releases14:51
ttxsince that could be a way for us to push git notes after the fact, solving the OSSA release note corner case14:51
dhellmannI'm behind on email, so I didn't see that one14:51
ttxhttp://lists.openstack.org/pipermail/openstack-dev/2015-August/072315.html14:51
dhellmannok, I'll read that more closely when we're done14:52
dhellmannI have to say though that I hesitate to use anything that circumvents the review process14:52
dhellmannor at least fails to take advantage of it14:53
ttxright, maybe I was crazy so sanity check is welcome. I blame philosophers and wine14:53
dhellmannthat's a good source of craziness :-)14:53
ttxsome say it's *the* source14:53
dhellmannI'm sure we could have a philosophical discussion of that over some wine14:53
ttxso yeah, this stable branch release thing is one of the few very time-sensitive things we haven't yet nailed in Liberty14:54
ttxIt would be great to also nail the pre/post discussion at some point, since that would likely start being applied on day 1 of Mitaka14:54
dhellmannyeah, it feels like we might want to just make a small change, like doing them on demand or something14:54
ttxdhellmann: even so we need the release notes generation mechanism14:55
ttxand that's likely to require more code than the other thing14:55
*** wshao has quit IRC14:55
dhellmanndo we not have a process for that now?14:56
dhellmannI guess I assumed we would keep doing the same thing14:56
ttxthe process is, every 3 to 6 months, you do them once for all integrated projects, with a stable release manager in charge of them14:56
dhellmannanteaya says hi (we're at breakfast)14:56
*** Kiall_ has joined #openstack-relmgr-office14:57
ttxdoesn't really scale to more projects or more often14:57
ttxhi!14:57
dhellmanntrue, unless we leave it up to the project teams to do the work14:57
ttxhmm, I guess that's a plan B. Ask them to write up some wiki page14:58
ttxand/or submit them as part of the openstack/releases request14:58
dhellmannI'm thinking about how we could use the releases repo, too. Maybe add a "release-notes" key and allow for an unreleased version at the end of a file14:58
dhellmannI guess if they include them in the actual release request we could leave tracking them up to the project, instead of trying to solve the whole problem14:59
ttxI kind of like the idea to generate them from the repo14:59
*** Kiall has quit IRC14:59
ttxso that people taking a random commit can still have not-too-bad release notes14:59
dhellmannyeah, that would be ideal15:00
ttxhence the proposal in the email to generate git notes from commit messages and the tag request15:00
dhellmannah, so you want to review it in the releases repo and push notes to the project repo15:01
dhellmannlike we do with tags -- I sort of like that15:01
ttxyep15:01
*** dims has joined #openstack-relmgr-office15:01
dhellmannok, I'll give that more thought when my head has woken up more15:01
ttxthe key issue is... you want to be able to fix an old commit, for example add an OSSA release note ref to the already-merged vulnerability fix15:02
ttxgit notes are handy, but not code-reviewed15:02
ttxbut if you use the mix I propose in the above email that would work15:02
ttxjust requires $CODE15:02
dhellmann++15:02
ttxand I do not overestimate how much work I can put in in the months before summit15:03
ttx:)15:03
ttxanyway, need to jump in call15:03
ttxgood to sync15:03
*** dims_ has quit IRC15:03
ttxI added underlines to all the liberty time-sensitive items15:04
dhellmannok, good to catch up, I'll give all of this more thought15:04
dhellmannack15:04
*** dims has quit IRC15:29
*** dims has joined #openstack-relmgr-office15:30
*** dims has quit IRC15:45
*** dims has joined #openstack-relmgr-office15:47
*** mestery has joined #openstack-relmgr-office15:54
*** wshao has joined #openstack-relmgr-office16:36
*** dims has quit IRC16:36
*** dims has joined #openstack-relmgr-office16:39
*** wshao has quit IRC16:49
*** dims has quit IRC16:54
*** dims has joined #openstack-relmgr-office16:57
*** dims_ has joined #openstack-relmgr-office17:02
openstackgerritKaitlin Farr proposed openstack/releases: python-barbicanclient 3.3.0  https://review.openstack.org/21428017:04
*** dims has quit IRC17:04
openstackgerritDavanum Srinivas (dims) proposed openstack/releases: Oslo Releases for week of Aug 17th, 2015  https://review.openstack.org/21428117:05
*** mestery has quit IRC17:07
openstackgerritDavanum Srinivas (dims) proposed openstack/releases: Adds oslo.service 0.7.0 deliverable  https://review.openstack.org/21200517:08
*** dims has joined #openstack-relmgr-office17:08
*** dims_ has quit IRC17:09
*** dims_ has joined #openstack-relmgr-office17:11
*** dims has quit IRC17:14
dims_dhellmann: releases for this week is ready - https://etherpad.openstack.org/p/library-releases17:14
dhellmanndims_: ack. I'm at the ops meetup, but I'll try to give them a look asap17:14
dims_thanks dhellmann, will wait for your OK before i cut releases17:15
dhellmannttx: the logging working group breakout session lines up with the cross-project meeting today17:17
*** dims_ has quit IRC17:20
*** dims has joined #openstack-relmgr-office17:20
*** dims has quit IRC17:20
*** dims has joined #openstack-relmgr-office17:21
*** wshao has joined #openstack-relmgr-office17:24
dimsdhellmann: i see a weird job failure http://logs.openstack.org/81/214281/1/check/gate-releases-tox-list-changes/b264d33/console.html#_2015-08-18_17_41_38_21717:51
*** wshao has quit IRC17:51
dhellmanndims: is that repeatable? did the node lose its disk or something?18:02
dimsrecheck-ing now18:03
dhellmanndims: ah, no, it's a bug in the script18:04
*** openstackgerrit_ has quit IRC18:11
openstackgerritDoug Hellmann proposed openstack/releases: Oslo Releases for week of Aug 17th, 2015  https://review.openstack.org/21428118:12
openstackgerritDoug Hellmann proposed openstack/releases: Make subprocess chdir instead of changing global state  https://review.openstack.org/21429318:12
dhellmanndims: ^^18:12
dimsthanks Doug18:13
dimsdhellmann: it's probably late for ttx, should i merge the chdir change?18:16
dhellmanndims: yeah, maybe we can get lifeless to take a look, but it might be the wrong time of day for him, too18:19
*** jroll has joined #openstack-relmgr-office18:25
jrolldhellmann: hi! wanting to do an ironic release. wondering how this was resolved in other projects https://review.openstack.org/#/c/192404/18:26
dhellmannjroll: you need to tag 2.0.0 then remove that line from the setup.cfg entirely. Those changes should happen without any intermediate patches, so you'll need to coordinate to make sure no cores approve patches while you're clearing the version18:28
openstackgerritMerged openstack/releases: Make subprocess chdir instead of changing global state  https://review.openstack.org/21429318:28
dhellmannjroll: as part of the release model change you're making, ironic will switch from pre-versioning to post-versioning, so you don't need that line18:28
jrolldhellmann: oh, neat. thanks!18:28
dhellmannjroll: I think the ironic acls are set so the release team needs to do the tagging for you, so to get that you should submit a patch to the openstack/releases repo (see the README there)18:31
jrollcool18:32
jrolldevananda: ^ fyi18:32
devanandaoh neat. lemme test that and see if it fixes pbr/pip fo rme18:38
jrolldevananda: if we can agree on HEAD being 2.0.0 I have a patch ready18:39
devanandaI think it's 4.0.0, fwiw18:39
devanandabecause I, J, K18:39
jrollyeah, just saw -ironic18:39
openstackgerritJim Rollenhagen proposed openstack/releases: Add Ironic 2.0.0  https://review.openstack.org/21430118:42
jrolldevananda: ^18:42
jrollwow, I'm terrible at numbers18:42
openstackgerritJim Rollenhagen proposed openstack/releases: Add Ironic 4.0.0  https://review.openstack.org/21430118:42
jrollmuch better18:42
devananda:)18:46
*** wshao has joined #openstack-relmgr-office18:56
dimsdhellmann: hoping to get the olso libs out this evening if possible18:58
*** wshao has quit IRC19:07
*** stevemar has joined #openstack-relmgr-office19:08
stevemarpoking the channel19:09
stevemarcan i use the new 'releases' repo to create an initial pypi package?19:09
stevemarfor instance....19:09
stevemarwe have https://github.com/openstack/heat-translator/ but it's unreleased so far19:09
stevemaroh, it looks like https://pypi.python.org/pypi/heat-translator has been created19:10
stevemaropenstackci is there too19:11
stevemarguess it should be all good to go if i just stick to pushing a 'releases' patch?19:11
dimsstevemar: sahdev is driving it?19:16
stevemardims: yes sir19:16
dimsstevemar: i don't think the release management team helps with those releases... probably wait for dhellmann to chime in19:28
dimshe's at the ops mid-cycle today19:28
stevemardims: its cool, i'm working with sahdev on this now19:29
stevemaroh? i was chatting with doug about something like this last time, in this channel19:29
dimsstevemar: cool. i am not quite sure.19:30
dimsstevemar: so still doing keystone?19:30
stevemardims: of course, keystone 4 life19:30
dims:) just making sure19:31
stevemardims: not gonna start working on heat :) just trying to help out sahdev19:31
dims++19:33
*** mestery has joined #openstack-relmgr-office19:44
dhellmanndims: +2 on the oslo releases, I'll let you approve and watch for it to merge19:53
dimsthanks19:53
dhellmannstevemar: heat-translator is not marked with release:managed in the governance repo, so I don't know if we handle those releases or not19:54
dhellmannstevemar: there's a heat-translator-release team19:55
dhellmannstevemar: I think that means the heat folks can either use the scripts from release-tools directly, or just push a tag19:56
*** sigmavirus24 is now known as sigmavirus24_awa19:57
stevemardhellmann: so what determines if a project is release:managed ?19:58
*** sigmavirus24_awa is now known as sigmavirus2419:58
dhellmannstevemar: they have to ask, and then we have to agree to do it19:59
dhellmannit's not a high bar, but not all projects want us to manage them and in some cases we opt not to do it, but to help with instructions for running the tools19:59
stevemardhellmann: vague criteria is vague :P19:59
dhellmannstevemar: indeed19:59
lifelessdhellmann: morning20:01
dhellmannlifeless: hi20:04
*** mestery has quit IRC20:08
lifelessdhellmann: you pinged ?20:10
*** mestery has joined #openstack-relmgr-office20:10
dhellmannlifeless: we were hoping for a review, but dims went ahead and approved it because the job was broken and preventing releases20:11
dhellmannlifeless: https://review.openstack.org/21429320:11
dhellmannlifeless: that should look familiar, since you suggested it last week :-)20:11
dimslifeless: dhellmann: ack :)20:11
dimsdhellmann: want me to take care of this? https://review.openstack.org/#/c/213707/ (oslotest for stable/kilo)20:47
openstackgerritMerged openstack/releases: Adds oslo.service 0.7.0 deliverable  https://review.openstack.org/21200520:55
openstackgerritMerged openstack/releases: Oslo Releases for week of Aug 17th, 2015  https://review.openstack.org/21428120:56
openstackgerritMerged openstack/releases: Add oslo_middleware 2.6.0 release  https://review.openstack.org/21379020:56
dhellmanndims: please21:01
*** stevemar has quit IRC21:05
openstackgerritMerged openstack/releases: Release oslotest 1.5.3 for stable/kilo  https://review.openstack.org/21370721:19
*** mestery has quit IRC21:25
*** sileht has quit IRC21:43
openstackgerritDavanum Srinivas (dims) proposed openstack-infra/release-tools: Bump pbr version to match g-r  https://review.openstack.org/21436321:44
*** sigmavirus24 is now known as sigmavirus24_awa22:18
*** dims_ has joined #openstack-relmgr-office23:20
*** dims has quit IRC23:22
*** krotscheck has joined #openstack-relmgr-office23:32

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