Monday, 2016-03-07

*** amotoki has quit IRC00:08
*** amotoki has joined #openstack-release00:11
*** amotoki has quit IRC00:14
*** amotoki has joined #openstack-release00:37
*** amotoki has quit IRC00:39
*** dims has quit IRC01:26
*** sdake has joined #openstack-release01:37
*** amotoki has joined #openstack-release01:37
*** sdake_ has joined #openstack-release01:44
*** sdake has quit IRC01:44
*** sdake has joined #openstack-release01:52
*** amotoki has quit IRC01:52
*** sdake_ has quit IRC01:55
*** sdake has quit IRC01:57
*** amotoki has joined #openstack-release02:11
*** nikhil has joined #openstack-release02:25
*** sdake has joined #openstack-release02:33
*** sdake has quit IRC02:40
*** amrith is now known as _amrith_03:35
*** sdake has joined #openstack-release03:51
*** sdake has quit IRC03:52
*** sdake has joined #openstack-release03:54
*** sdake has quit IRC04:11
*** sdake has joined #openstack-release04:12
*** sdake has quit IRC04:21
*** amotoki has quit IRC05:25
*** amotoki has joined #openstack-release06:06
*** SAshish has joined #openstack-release06:27
SAshishHi All06:29
*** sridhar_ram has joined #openstack-release06:34
*** SAshish has quit IRC06:48
*** sorantis has joined #openstack-release06:48
sorantisHi. I was wondering if I can get some help with this one
patchbotsorantis: patch 280295 - requirements - Add kingbird to the list of projects06:49
*** sridhar_ram has quit IRC06:50
sorantisCan I ask to make an exception for kingbird to be added to the requirements list?06:58
*** amotoki has quit IRC07:00
*** amotoki has joined #openstack-release07:03
-openstackstatus- NOTICE: gerrit is going to be restarted due to bad performance07:24
*** ChanServ changes topic to "gerrit is going to be restarted due to bad performance"07:24
*** ChanServ changes topic to "OpenStack Release Managers office - Where weekly 1:1 sync points between release manager and PTLs happen - Logged at"07:27
*** sdake has joined #openstack-release07:33
*** sorantis has quit IRC07:39
*** amotoki has quit IRC07:50
*** jd__ has quit IRC07:56
*** jd__ has joined #openstack-release07:56
*** sorantis has joined #openstack-release08:09
*** amotoki has joined #openstack-release08:13
*** sdake has quit IRC08:21
*** pcaruana has joined #openstack-release08:25
*** daemontool_ has joined #openstack-release08:43
*** daemontool has quit IRC08:47
*** amotoki has quit IRC09:03
*** jd__ has quit IRC09:16
*** jd__ has joined #openstack-release09:16
*** dtantsur|afk is now known as dtantsur09:50
*** amotoki has joined #openstack-release09:56
*** daemontool_ has quit IRC10:16
*** sorantis has quit IRC10:17
openstackgerritMerged openstack/releases: move the check for the SHA to match HEAD earlier
openstackgerritMerged openstack/releases: merge pbr deliverable files into independent directory
*** amotoki has quit IRC10:25
*** daemontool has joined #openstack-release10:35
openstackgerritMerged openstack/releases: Astara mitaka-3 milestone release
*** dims_ has joined #openstack-release10:41
*** sorantis has joined #openstack-release10:43
*** dims_ has quit IRC11:09
*** sdague has joined #openstack-release11:14
*** dims_ has joined #openstack-release11:22
*** sdague has quit IRC11:59
*** amotoki has joined #openstack-release12:06
*** _amrith_ is now known as amrith12:14
*** sorantis has quit IRC12:26
*** gordc has joined #openstack-release12:32
*** sdague has joined #openstack-release12:43
*** nikhil has quit IRC12:58
*** Kiall has quit IRC13:03
*** Kiall has joined #openstack-release13:03
*** Kiall has quit IRC13:03
*** Kiall has joined #openstack-release13:03
*** amrith is now known as _amrith_13:03
dhellmannttx: I thought I'd go ahead and process that nova stable release, unless you can see a reason to wait?13:12
*** sorantis has joined #openstack-release13:17
dims_dhellmann : ttx : travelling today (day trip to NYC for bug smash) fyi13:24
dhellmanndims_ : ack, happy squashing13:24
dims_thanks dhellmann :)13:25
*** dims_ has quit IRC13:25
*** sorantis has quit IRC13:37
openstackgerritMerged openstack/releases: liberty: release nova 12.0.2
*** sdake has joined #openstack-release13:57
*** sdague has quit IRC14:23
openstackgerritDoug Hellmann proposed openstack/releases: fix the ironic-inspector liberty release notes link
*** _amrith_ is now known as amrith14:36
*** mriedem has joined #openstack-release14:42
*** sridhar_ram has joined #openstack-release14:48
*** dims has joined #openstack-release14:54
*** sigmavirus24_awa is now known as sigmavirus2414:56
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: ignore existing default branch when setting new default branch
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: make args to creating stable branch more explicit
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: add script to generate branching instructions
*** sdake_ has joined #openstack-release15:25
openstackgerritMerged openstack/releases: fix the ironic-inspector liberty release notes link
*** amotoki has quit IRC15:27
*** sdake has quit IRC15:29
*** sridhar_ram has quit IRC15:40
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: dump a release tracking dashboard
*** sdague has joined #openstack-release15:56
*** sigmavirus24 is now known as sigmavirus24_awa15:57
*** sigmavirus24_awa is now known as sigmavirus2415:57
*** nikhil has joined #openstack-release16:06
*** sdake_ is now known as sdake16:35
*** david_lyle has quit IRC16:46
*** david_lyle has joined #openstack-release16:46
*** dguitarbite has joined #openstack-release16:54
dhellmanndguitarbite : hi!17:14
dhellmanndguitarbite : ttx and I were reviewing the release model tags on projects last week, and found that training-labs is set to release:cycle-with-milestones but it doesn't have any recent tags17:15
dhellmannor branches, actually, since the most recent I see is kilo17:15
dhellmanndguitarbite : are you still releasing the labs in the same way, or should we see if another model tag makes more sense?17:16
dguitarbitedhellmann: hi, Im here17:23
dguitarbitedhellmann: We have decided to use branches for releases. I have to release liberty.17:23
dguitarbiteI am waiting for getting the success rate from 96~97% to 99 % hopefully more but atleast 99%17:24
dhellmannso you'll be creating the branch and preparing a release from that branch?17:24
dguitarbiteSome technical problems on the RAM size for liberty.17:24
dguitarbitedhellmann: yes that is the plan.17:24
dhellmannwell, vice versa actually, since we want branches created from tags, but yeah17:24
dguitarbiteIf you want, I could move to creating tags17:25
dhellmanntheoretically you'd do both17:25
dguitarbiteThe reason why I moved away from it is to avoid feature branches. Its easier for the working style of training-labs team.17:25
dhellmanncreate the tag to trigger the release, and then create a branch from that tag for updates to the release17:25
dguitarbitedhellmann: ok, Ill change that. Should I also do the same for older releases?17:25
dhellmannif you're not tagging now, how are you actually producing a release artifact?17:26
dhellmannand what artifacts are produced from that repo (sorry, I don't know what it is)?17:26
dguitarbiteI actually dont know what is a release artifact. The repository is barely 6 months old.17:26
dguitarbiteDo you have a link?17:26
dhellmannusually when we say we're making a release we build something from the repository and publish it separately17:27
dhellmannso for python code we might prepare a package and upload it to or make a tarball and post it to tarballs.openstack.org17:27
dguitarbiteAhh, yes I just got that patch merged in infra:
dhellmanndo you do something like that? or do you just create the branch at the point where you want to have a release?17:27
dguitarbiteWe are publishing tar balls which are a bit different from other projects since we just need some specific parts of the repo.17:27
dhellmannah, good17:28
dguitarbiteSo the current script takes the branch name from Zuul/Jenkins job and creates a tarball from there17:28
dguitarbiteDo I need to do more? I can change it easily since its quite the beginning of the project.17:29
dhellmannthe tarballs you have now will be updated in place each time a new commit is made on one of those branches17:29
dhellmannthat's useful for someone tracking the branch, but it's not a reproducable release in the sense that a tag is17:29
dguitarbiteOk, I think I understand your point here. I can freeze the releases and create stable tarballs and then the release-current tarballs (which is what is happening now)17:30
dguitarbiteSo tags are really handy for that I assume.17:31
dhellmannthat's right17:31
ttxdhellmann: traveling Tue-Fri, should be online from time to time, but expect delays17:31
dhellmannit's the difference between being able to point at something that's always the same, and something that is updated over time17:31
dhellmannttx: ack, np17:31
dguitarbiteok, now it makes more sense to me! Thanks :)17:32
dhellmanndguitarbite : so I think what we want to do is set up the jobs that produce releases based on tags, and then decide on a version numbering scheme (you have to use numbers, not names), and then we can set up the tagging information in the openstack/releases repository17:32
dhellmannthen the release team can help you prepare releases when you're ready for them17:32
dguitarbitedhellmann: There is a python port I am working on at present. Does it make more sense to do this after the port or I should do it right away? ETA for the port is around 2-3 months before I start pushing it into the repo.17:33
dhellmanndguitarbite : I recommend using 1.0.0 for the earliest release, and increasing to 2.0.0, etc. for each series. That way within a series if you have updates, you can increment the minor version number (1.1.0) for new features and the patch version number (1.0.1) for bug fixes17:33
dhellmanndguitarbite : we could start with your existing releases, and set the pattern to use for the upcoming releases17:34
dhellmanndguitarbite : the other aspect of the release model tag is *when* releases are produced17:35
dhellmannif you're intending to release something new at the end of each cycle, a model like cycle-with-milestones or cycle-with-intermediary makes sense17:35
dguitarbiteOk, I guess I could get Liberty to be v1.0.0 does not make much sense to do that for icehouse/kilo/juno since they will be EOL/not supported very soon.17:35
dhellmannbut if you're releasing any time and not in sync with the milestone, using the independent release model makes more sense17:35
*** sdake_ has joined #openstack-release17:35
dhellmanndguitarbite : I suppose, though to be accurate you could go back and tag all of those older releases, too. it's up to you.17:36
dguitarbitedhellmann: So, there will be one major release with other openstack projects for sure. The intermediaries are a bit more random but I could discuss this with the team and get a 2/3 milestone based approach too.17:37
dhellmannfor the milestone model, we really do expect you to be ready to prepare something on those deadlines, so if you're not sure about that I recommend cycle-with-intermediary17:38
*** sdake has quit IRC17:38
dhellmannthe important thing is to accurately reflect what you want to do, so that consumers can understand what to expect17:38
dguitarbitedhellmann: I think I can visualize a 6 months cycle with a major release and intermediary for starting to work on the next release of OpenStack. Since we have two sides of devel. Library and deployment scripts, second part is in sync with install-guides,.17:41
dhellmanndguitarbite : that makes sense17:42
dguitarbiteso 1.0.0, 2.0.0 for major releases: 1.1.0, 2.1.0 for intermediaries and then 1.1.1 for bug fixes etc. which are totally random.17:42
dhellmannthat's right17:43
dhellmannwe would create branches from the major releases, and the updates would be tagged on those branches17:43
dguitarbitemakes sense.17:44
dguitarbitedhellmann: Awesome! Now I need to realize this model, a bit scared of infra but I think I could figure it out. Any links handy? I will ofcourse wait till the next team meeting and get votes from the entire team on this.17:44
dhellmannI can help you figure out which jobs you need17:45
dhellmannif you look at the publish-to-pypi macro at the top of zuul/layout.yaml that should give you some idea17:45
dhellmannyou won't want all of them, though17:45
dhellmannactually, openstack-server-release-jobs is a closer fit17:45
dhellmannin fact, you could probably use that as-is17:46
* dguitarbite checking out openstack-infra repo. project-config17:47
dhellmanndguitarbite : the other thing to do is update the tag in the governance repo to cycle-with-intermediary. If you do that, ttx and I can vote on and approve it17:47
dguitarbitedhellmann: Ok, I will do it. Does the governance patch go in first or the infra job nneeds to go in first17:49
dhellmanndguitarbite : the order doesn't matter for those17:50
dguitarbitedhellmann: ok, so I will publish the governance job on Wed. after the team meeting17:52
dhellmanndguitarbite : sounds good, I'll watch for it17:52
dguitarbitedhellmann: yes, thanks a lot. Anything else?17:53
*** amrith is now known as _amrith_17:57
*** _amrith_ is now known as amrith17:58
dhellmanndguitarbite : no, I think that covers everything, thanks17:59
dguitarbitedhellmann: Thanks a lot! :).18:00
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: add script to generate branching instructions
*** doug-fish has quit IRC18:07
*** doug-fish has joined #openstack-release18:08
*** sridhar_ram has joined #openstack-release18:10
*** dtantsur is now known as dtantsur|afk18:11
*** sorantis has joined #openstack-release18:12
*** doug-fish has quit IRC18:13
*** sdake_ has quit IRC18:17
*** doug-fish has joined #openstack-release18:27
*** kzaitsev_mb has joined #openstack-release18:34
*** sigmavirus24 is now known as sigmavirus24_awa18:37
*** sigmavirus24_awa is now known as sigmavirus2418:57
*** sorantis has quit IRC19:00
*** rockyg has joined #openstack-release19:02
*** doug-fis_ has joined #openstack-release19:03
*** doug-fi__ has joined #openstack-release19:04
*** doug-f___ has joined #openstack-release19:05
*** doug-fish has quit IRC19:06
*** doug-fish has joined #openstack-release19:06
*** kzaitsev_mb has quit IRC19:07
*** doug-fis_ has quit IRC19:08
*** doug-fi__ has quit IRC19:09
*** doug-f___ has quit IRC19:10
*** amrith is now known as _amrith_19:15
*** gordc has quit IRC19:16
*** _amrith_ is now known as amrith19:21
*** sdake has joined #openstack-release19:31
*** sridhar_ram1 has joined #openstack-release19:35
*** sridhar_ram has quit IRC19:37
*** doug-fish has quit IRC19:38
*** mhayden has joined #openstack-release19:41
mhaydenis this the right place to ask about the openstack/requirements repo?19:41
mhaydenif so, i have a question around bumping the max version for python-openstackclient in kilo to 1.6.0 to bring in the internalURL fix19:44
mhaydenif i am totally crazy for suggesting this, please let me know :)19:44
*** rockyg has quit IRC19:50
*** doug-fish has joined #openstack-release19:53
*** kzaitsev_mb has joined #openstack-release19:54
*** gchung has joined #openstack-release19:58
*** gchung is now known as gordc19:58
*** kzaitsev_mb has quit IRC19:59
*** rockyg has joined #openstack-release20:04
*** doug-fish has quit IRC20:05
*** doug-fish has joined #openstack-release20:06
*** rockyg has quit IRC20:09
*** doug-fis_ has joined #openstack-release20:10
*** doug-fish has quit IRC20:11
*** david-lyle_ has joined #openstack-release20:12
*** david_lyle has quit IRC20:13
*** sridhar_ram1 is now known as sridhar_ram20:22
*** david-lyle_ is now known as david-lyle20:26
*** sigmavirus24 is now known as sigmavirus24_awa20:58
*** stevemar has quit IRC20:59
*** stevemar has joined #openstack-release21:01
*** amrith is now known as _amrith_21:01
*** dims has quit IRC21:07
*** sdake has quit IRC21:07
*** sdague has quit IRC21:09
*** sigmavirus24_awa is now known as sigmavirus2421:16
*** kzaitsev_mb has joined #openstack-release21:35
*** sigmavirus24 is now known as sigmavirus24_awa21:41
*** sigmavirus24_awa is now known as sigmavirus2421:42
*** kzaitsev_mb has quit IRC21:43
*** kzaitsev_mb has joined #openstack-release21:50
sridhar_ramdhellmann: ping, need your guidance to work out a release plan for tacker.. whenever you've sometime21:53
*** dims has joined #openstack-release21:58
*** dims has quit IRC22:01
*** david-lyle has quit IRC22:02
*** david-lyle has joined #openstack-release22:02
*** doug-fis_ has quit IRC22:20
*** doug-fish has joined #openstack-release22:20
*** doug-fish has quit IRC22:23
*** doug-fish has joined #openstack-release22:24
*** stevebaker has quit IRC22:25
*** doug-fish has quit IRC22:26
*** doug-fish has joined #openstack-release22:26
stevemarmhayden: i don't think that's possible, we released 1.6.0 and a lot of previous versions in liberty
dhellmannmhayden : you want to raise the maximum version? not the minimum?22:32
dhellmannmhayden : for stable branches, you probably want to ask in #openstack-stable22:32
dhellmannsridhar_ram : what tz are you in? it's close to the end of my day here on the east coast of the us22:33
sridhar_ramdhellmann: I'm in PST22:33
dhellmannsridhar_ram : ok, maybe we can connect tomorrow in your morning?22:33
sridhar_ramdhellmann: ... and yes, it won't be a quick one!22:33
sridhar_ramdhellmann: sure... when does your typical office hrs start ?22:34
dhellmannsridhar_ram : 9 am-ish EST22:34
sridhar_ramdhellmann: sounds good.. will ping tomorrow morning. Thanks22:34
dhellmannsridhar_ram : sounds good22:35
*** mriedem is now known as mriedem_away22:44
*** doug-fish has quit IRC22:53
openstackgerritDoug Hellmann proposed openstack/reno: always show coverage report for test runs
openstackgerritDoug Hellmann proposed openstack/reno: improve test coverage
openstackgerritDoug Hellmann proposed openstack/reno: refactor argument buildup to make it more reusable
openstackgerritDoug Hellmann proposed openstack/reno: add 'cache' command to write a cache file
openstackgerritDoug Hellmann proposed openstack/reno: use the cache file instead of scanner when possible
openstackgerritDoug Hellmann proposed openstack/reno: make the cache command write to a file by default
dhellmannttx, lifeless: that patch series ^^ sets us up to add reno support to pbr so we can start including release notes in sdists22:57
dhellmannthe loader probably needs more tests, but it's been a long day22:57
*** doug-fish has joined #openstack-release23:01
*** mtreinish has quit IRC23:13
*** mtreinish has joined #openstack-release23:14
*** sigmavirus24 is now known as sigmavirus24_awa23:30
*** gordc has quit IRC23:32
*** doug-fish has quit IRC23:37

Generated by 2.14.0 by Marius Gedminas - find it at!