Thursday, 2015-09-10

*** rossella_s has quit IRC01:06
*** rossella_s has joined #openstack-neutron-release01:06
*** yamamoto has joined #openstack-neutron-release03:01
*** rossella_s has quit IRC05:06
*** rossella_s has joined #openstack-neutron-release05:06
*** amotoki has joined #openstack-neutron-release07:55
*** yamamoto_ has joined #openstack-neutron-release08:44
*** yamamoto has quit IRC08:44
*** yamamoto has joined #openstack-neutron-release08:44
*** yamamoto_ has quit IRC08:48
*** salv-orl_ has joined #openstack-neutron-release09:56
*** salv-orlando has quit IRC10:00
*** salv-orl_ has quit IRC10:04
*** salv-orl_ has joined #openstack-neutron-release10:05
*** salv-orl_ has quit IRC10:10
*** salv-orlando has joined #openstack-neutron-release10:11
*** salv-orl_ has joined #openstack-neutron-release10:13
*** salv-orlando has quit IRC10:16
*** salv-orlando has joined #openstack-neutron-release10:25
*** salv-orl_ has quit IRC10:26
*** salv-orl_ has joined #openstack-neutron-release10:48
*** salv-orlando has quit IRC10:51
*** salv-orl_ has quit IRC10:51
*** salv-orlando has joined #openstack-neutron-release10:52
*** salv-orl_ has joined #openstack-neutron-release11:21
*** salv-orl_ has quit IRC11:24
*** salv-orl_ has joined #openstack-neutron-release11:24
*** salv-orlando has quit IRC11:25
*** salv-orl_ has quit IRC11:34
*** salv-orlando has joined #openstack-neutron-release11:35
*** salv-orl_ has joined #openstack-neutron-release12:23
*** salv-orlando has quit IRC12:27
*** salv-orlando has joined #openstack-neutron-release12:29
*** salv-orl_ has quit IRC12:30
*** salv-orl_ has joined #openstack-neutron-release12:36
*** salv-orlando has quit IRC12:36
*** yamamoto has quit IRC12:56
*** carl_baldwin has joined #openstack-neutron-release14:14
*** salv-orl_ has quit IRC14:43
*** yamamoto has joined #openstack-neutron-release14:43
*** salv-orlando has joined #openstack-neutron-release14:43
*** salv-orlando has quit IRC14:44
*** salv-orlando has joined #openstack-neutron-release14:44
*** salv-orlando has quit IRC15:15
*** yamamoto has quit IRC16:56
*** salv-orlando has joined #openstack-neutron-release17:24
*** salv-orlando has quit IRC17:29
*** salv-orlando has joined #openstack-neutron-release17:30
*** salv-orlando has quit IRC17:48
*** yamamoto has joined #openstack-neutron-release17:57
*** yamamoto has quit IRC18:02
*** carl_baldwin has quit IRC18:18
*** salv-orlando has joined #openstack-neutron-release19:04
*** salv-orlando has quit IRC19:12
*** carl_baldwin has joined #openstack-neutron-release19:13
HenryGmestery: ping19:16
HenryGmestery: what does it take to create a feature branch in a stadium repo?19:17
HenryGkevinbenton: maybe you know?19:17
*** carl_baldwin has quit IRC19:19
kevinbentonHenryG: i think kyle or armando19:22
kevinbentonHenryG: need to do it19:22
kevinbentonor dougwig19:23
dougwigttx or dhellman, i think.19:23
dougwigdepends on who has create perms in the gerrit acls.19:23
dougwigand be SURE to name it "feature/*", or the ci scripts will puke.19:23
kevinbentonoh yeah, sorry i was thinking of a merge commit19:23
kevinbentonnot creating a branch19:24
dougwigHenryG: what repo?19:24
HenryGdougwig: guess ;)19:24
dougwignetworking-flavor-chaining ?19:24
HenryGno, networking-intent19:24
mesteryNo19:26
mesteryWe can create those19:26
dougwigi can create them in a lot of networking-.  if it's neutron, ask ttx.19:26
mesteryfeature branches19:26
dougwigaha, there's the man.19:26
mesteryWell, dougwig, I think you can do it for Neutron as well to be honest using gerrit19:26
dougwigi tried.  let me look again.19:26
mesteryexervising19:26
mesteryOK19:26
mesterychecking as well19:26
dougwigi don't see anything but a display list.19:27
dougwigof branches19:27
HenryGOnce my feature branch is created, is there some documentation on how to resync to master (which we would need to do periodically) and how to collapse to master when the feature is done?19:30
*** carl_baldwin has joined #openstack-neutron-release19:33
*** salv-orlando has joined #openstack-neutron-release19:46
*** amotoki has quit IRC20:03
kevinbentonHenryG: resyncing is a pain20:04
kevinbentonHenryG: you have to have dougwig, mestery, or armax propose a merge commit20:04
mesteryHenryG: What are you using the feature branch for by chance?20:04
kevinbentonHenryG: i think feature branches are not worth the effort if you can avoid them :(20:04
HenryGWhy can't it be as easy as 'git rebase master' ?20:05
kevinbentonHenryG: rebasing changes all of the commits20:05
*** salv-orlando has quit IRC20:05
kevinbentonHenryG: you can't push a rebase to a remote tree20:05
kevinbentonbecause it's changing history20:06
dougwigHenryG: here's the docs for it: http://docs.openstack.org/infra/manual/drivers.html20:07
dougwigHenryG: in neutron, you need to find someone in the neutron-release group to do the steps.20:07
HenryGI want feature branches because teams of people work on a feature in some private clone repo somewhere and then suddenly show up with a titanic code dump.20:07
HenryGI would prefer to give them a way to work openly upstream.20:08
kevinbentonunfortunately what happens (at least with neutron) is that people are working upstream, but nobody is reviewing everything that goes in20:09
kevinbentonand then when the merge commit comes around, there is no good way to review it20:09
*** salv-orlando has joined #openstack-neutron-release20:15
*** salv-orlando has quit IRC20:16
*** salv-orlando has joined #openstack-neutron-release20:31
mesteryHenryG: what kevinbenton said there21:14
HenryGmestery: so what is the solution to allow folks to work openly on a big feature that may be disruptive to master, or may not be release-ready until the next cycle?22:12
*** carl_baldwin has quit IRC22:36
*** carl_baldwin has joined #openstack-neutron-release22:45
*** salv-orl_ has joined #openstack-neutron-release22:56
*** salv-orlando has quit IRC22:59
*** salv-orl_ has quit IRC23:43
*** yamamoto has joined #openstack-neutron-release23:48

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