Wednesday, 2016-09-07

prometheanfiretonyb: https://review.openstack.org/365565 that look ok?00:01
tonybprometheanfire: I haven't looked yet00:01
tonybprometheanfire: I'll need to check how many libraries that affects00:02
prometheanfirek00:02
prometheanfiretonyb: well, we already need to bump oslo.db and block at least 4.13.100:03
prometheanfirebased off of https://review.openstack.org/#/q/is:open+starredby:tonyb+branch:master+project:openstack/requirements at least :D00:03
tonybprometheanfire: Right the u-c part is fine, it'd the g-r part that worries me00:03
prometheanfireya00:04
prometheanfiretonyb: how many things are you core on now?02:11
tonybprometheanfire: Oh a few, stable-maint, nova-stable, election, requirements, "calendar" and nominated for release management possibly others02:12
prometheanfirewe need to get you core on more02:13
prometheanfireobviously02:13
tonybprometheanfire: it's been a fun couple of years02:13
tonybprometheanfire: Yeah all-the-things02:13
prometheanfireI wonder, between all the projects you work on, and sigmavirus, who has more02:14
tonybprometheanfire: Oh totally sigmavirus02:16
prometheanfireI'm not so sure02:18
*** coolsvap_ has joined #openstack-requirements03:50
*** openstackgerrit has quit IRC05:18
*** openstackgerrit has joined #openstack-requirements05:19
*** stevemar has joined #openstack-requirements06:44
*** jpena|off is now known as jpena07:03
openstackgerritOpenStack Proposal Bot proposed openstack/requirements: Updated from generate-constraints  https://review.openstack.org/36476207:18
*** armax has quit IRC07:31
*** openstackgerrit has quit IRC08:34
*** openstackgerrit has joined #openstack-requirements08:34
openstackgerritJames Page proposed openstack/requirements: Set minimum positional version to 1.1.1  https://review.openstack.org/36663109:42
*** jpena is now known as jpena|lunch11:49
prometheanfirewoo, not me this time11:56
*** coolsvap_ is now known as coolsvap12:01
*** jpena|lunch is now known as jpena12:48
tonybprometheanfire: I use NTP also, and we disagree on the time13:00
dirkif it helps, prometheanfire was also early for my ntp13:01
dirkmaybe he's in the future ntp zone13:01
tonybtoabctl: WRT os-vif mreidem was very 'meh' on an FFE13:01
prometheanfire:P13:01
tonybtoabctl: said it was up to neutron PTL13:02
tonybI'm fine with doign FFE13:02
toabctlhm13:02
tonybs esp for u-c bumps as long as they're well thought out13:02
tonybI kinda think if it's too much work to write an email then it isn't important13:03
dirktonyb: so for os-vif, since it is about fixing a gating issue, we should be doing a FFE ?13:03
toabctldirk, how can it fix a gating issue if it isn't used in the gate?13:03
dirkI would assume the assumption of the core group who approved that change was that it would end up in the gating13:04
toabctlafaiu the whole new os-vif release is used nowhere.13:04
dirkthats why I think we need to have the uc change merged13:04
tonybdirk: Sure you can write the FFE but we'll need buy-in from nova, neutron and (to a lesser extent) release management13:04
dirktonyb: ok, is the FFE process documented somewhere?13:04
dirkif all it needs is an email I can write email :)13:04
tonybdirk: then go forth and write an email add [requirements][FFE] to the subject13:05
tonybdirk: and possbly [nova][neutron]13:05
tonybthen we can as a whole community discuss it13:05
tonybI can give my thoughts on the impact to $projects13:06
tonybdirk: Like I said the impact on a u-c bump is pretty manageable really it's downstream that pay the highest price and y'all have already said you're not keeping up so ....13:06
dirktonyb: well, we want to keep up with the version and package the right one13:08
dirkand thats why I'm trying to figure out which one should be packaged :)13:09
tonybdirk: So the current statement has been that from requirements freeze dirstro's shoudl agressivly target packaging versions from u-c13:09
tonybthe ammoun of churn there is minimal at this stage and so on13:10
tonybso I admit I'm not tied to a distro but I thought that was preety well understood13:10
prometheanfireok, email sent13:11
tonybprometheanfire: cool, I'll reply tomorrow afternoon, as I'll need to assess the secondary impacts of the positional change13:11
prometheanfireyarp13:11
dirktonyb: I'm good with that.13:11
prometheanfireI mentioned knock on effects as a negative13:11
tonyband that means writing more code to do that assessment13:11
dirktonyb: just wanted to make sure we're aligned..13:12
tonybdirk: okay.13:12
prometheanfireas a packager I wait til rc1 generally13:12
dirktonyb: and as we seem to have a plan to fix that potentially post-branching its even better13:12
tonybprometheanfire: Sure that's much the same thing13:12
prometheanfirehonestly the week before the release sees the most work13:12
prometheanfireI've been bitten by updates coming in late too many times :P13:13
tonybprometheanfire: Huh that surprises me.  I can imagin nova or cinder causing a probalem but less so stuff from requirements13:14
prometheanfiretonyb: don't we already have an FFE for the oslo.db bump?13:14
prometheanfireI don't package everything from requirements13:14
prometheanfiremy actual target is nova/cinder13:14
tonybprometheanfire: No, but we can tack one onto the existsing thread, the u-c change is ok from my POV13:14
prometheanfireso I have to wait for the knock on effects to settle down13:15
prometheanfireya, oslo.db can have the != stuff backported13:15
prometheanfireso it's better13:15
prometheanfireeasier13:15
tonybyeah13:15
prometheanfireI'm in favor of that, want me to -W the blocking bug?13:16
prometheanfirealso13:16
prometheanfiredo we want to unmask pymysql 0.7.7 once these things go in?13:16
tonybprometheanfire: I think we've missed the boat on pymysql13:17
prometheanfirethat can be backported too, don't see a reason why it can't at least13:18
tonybprometheanfire: Sure it can be backported13:18
prometheanfirethat's what I was meaning13:18
tonybprometheanfire: I know I was agreeing with you13:19
prometheanfire:D13:19
prometheanfireviolent agreement13:19
prometheanfireok, second FFE sent13:23
prometheanfirethink that's it (for me)13:23
prometheanfiretonyb: nn13:23
tonybprometheanfire: Yeah I shoudl do that thing.13:24
dimstonyb : late night or early morning? :)13:46
prometheanfirewhy not both?14:00
dims:)14:01
*** number80 has quit IRC14:20
*** anteaya has quit IRC14:20
*** number80 has joined #openstack-requirements14:24
*** anteaya has joined #openstack-requirements14:42
*** armax has joined #openstack-requirements15:27
*** sigmavirus is now known as irvirus16:40
*** irvirus is now known as sigmavirus16:40
*** jpena is now known as jpena|away17:19
*** number80 has quit IRC17:20
*** number80 has joined #openstack-requirements17:21
*** sridhar_ram is now known as sridhar_ram_afk17:52
*** sridhar_ram_afk is now known as sridhar_ram18:37
*** openstackgerrit has quit IRC20:04
*** openstackgerrit has joined #openstack-requirements20:04
openstackgerritHongbin Lu proposed openstack/requirements: Release docker-py version constraint  https://review.openstack.org/36694820:19
tonybdims: late night ....20:41
prometheanfiretonyb: :D20:44
prometheanfirewoo, removing python3.3 from the tree now :D21:38
prometheanfireoops, wrong channel21:38
*** jmccrory has quit IRC21:53
*** jmccrory has joined #openstack-requirements21:53
*** jmccrory has quit IRC21:55
*** jmccrory has joined #openstack-requirements21:55
*** jmccrory has quit IRC21:57
*** jmccrory has joined #openstack-requirements21:57
*** armax has quit IRC22:58
*** armax has joined #openstack-requirements23:50

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