Friday, 2015-06-12

*** carl_baldwin has joined #openstack-neutron-release01:59
*** carl_baldwin has quit IRC03:28
*** amuller has joined #openstack-neutron-release13:35
*** carl_baldwin has joined #openstack-neutron-release14:57
*** amuller is now known as amuller_afk17:41
*** amuller_afk is now known as amuller18:04
amullermestery: I wanted to discuss cores merging patches without another +2, taking this patch as an example: https://review.openstack.org/#/c/191156/18:19
amullerOther examples would be fixing spelling mistakes in green text18:20
amullerI argue that we should do more of that18:20
amullerdougwig: HenryG: kevinbenton: carl_baldwin: thoughts?18:22
carl_baldwinAh, the “ninja merge”.18:24
kevinbentoni can see maybe spelling mistakes, but i don't think we should go down that path for ones that touch real code should18:24
carl_baldwinI’ve personally been careful with ninja merging.18:24
carl_baldwinI agree about touching real code in general.  Even simple looking changes can sometimes benefit from a second eye.18:25
kevinbentoni don't see why this needs to merge so quickly18:26
amullerNeed is a strong word :)18:27
HenryGI do like to see trivial patches merge quickly and not waste too many people's time18:30
kevinbentonthat only took me like 30 seconds to review, not worth changing process18:31
HenryGHowever, I feel better with the 2-person safety check most of the time18:31
carl_baldwinI’ll admit to a handful of ninja merges when a patch already had another +2 and I wanted a trivial change to commit message or comment or something.  I generally note in the gerrit comment why I merged without a second +2.18:31
carl_baldwinBut, I do agree in general with the 2-person safety check too.18:32
HenryGWith more core reviewers coming on board I think we can get 2 eyes on trivial changes more quickly more often now18:33
carl_baldwinHenryG: ++18:33
HenryGAnd like kevinbenton said, 30 seconds x 2 is not a big deal18:34
amullerThat is true Henry18:34
* amuller is reading Nova vif drivers code. Bleargh.18:35
dougwigBots, trivial, or rebases, I only do one.  But trivial for me means typos or white space.  I'm open to other.19:15
dougwigOr less19:15
mesteryI'm not in favor of having a single +2 for even simple merges19:29
mesteryMy reasoning is it's never hard to find someone else to do the second +2 :)19:29
mesteryAt least, I've not had a problem.19:29
mesteryBut that may just be me19:29
HenryGThe only thing worse than having your +2 on a patch that breaks the gate is having the only +2 on the patch that breaks the gate. ;)19:46
* carl_baldwin was thinking the same thing.19:54
mestery+100020:40
amullerkevinbenton: I'm starting to think that 'RFE' is like a red hat thing or something22:49
amullereveryone I work with use it a lot22:49
amullerno one else seems to know what it means22:49
kevinbentoni think so22:49
kevinbentoni had never heard it before you folks infected neutron with it :)22:49
amullerhah22:49
amullermission accomplished22:49
*** amuller has quit IRC22:59
*** carl_baldwin has quit IRC23:14
HenryGWhat is the state for an RFE bug before the drivers team discusses it?23:41
HenryGAh "confirmed" (found it in the "blueprints" policies :)23:42

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