tonyb | prometheanfire: the mitmproxy thiing happend because our XFAILS stuff is buggy | 00:11 |
---|---|---|
tonyb | manjeets: I'll need to read the logs etc and that's a complex issue :/ | 00:12 |
*** tosky has quit IRC | 00:12 | |
manjeets | http://logs.openstack.org/15/579915/16/check/requirements-check/15c3826/job-output.txt.gz#_2018-07-17_18_08_16_940762 | 00:12 |
manjeets | tonyb, is there a way to add exception for packages in requirements.txt | 00:13 |
manjeets | ? | 00:13 |
tonyb | manjeets: No | 00:13 |
manjeets | tonyb, https://review.openstack.org/#/c/579915/ this is the patch | 00:13 |
tonyb | manjeets: Like I said it's complex | 00:13 |
tonyb | manjeets: Thanks | 00:13 |
manjeets | I cherry picked some changes to stable/queens to fix the gate | 00:13 |
tonyb | manjeets: Okay I suspect that you just need to deal with the conflicts | 00:15 |
manjeets | tonyb, sorry I didn't get that ? what conflicts ? | 00:15 |
tonyb | manjeets: I think on stable/queens you need to leave the tox_install stuff in place so it isn't an actual Conflict in git terms but it is in functaionality chnages | 00:16 |
tonyb | manjeets: but it's all very confusing | 00:16 |
tonyb | manjeets: Yup I *think* if you leave the tox_install.sh stuff in place and remove the chnages to requirements.txt things will work as expected | 00:28 |
manjeets | tonyb, I tried that earlier it failed almost all jobs, but i'll looking at it, will try again | 00:28 |
manjeets | im looking at it** | 00:28 |
manjeets | tonyb, thanks | 00:28 |
tonyb | manjeets: Can you tell me which PS does it that way? | 00:29 |
manjeets | tonyb, https://review.openstack.org/#/c/576110/ PS 8 | 00:30 |
manjeets | I think if i just cherry-pick stestr stuff and leave tox_install that may work | 00:30 |
manjeets | I just looked at the logs mostly complaining stestr | 00:30 |
tonyb | manjeets: Okay that doesn't really make sense but it's worth a try | 00:32 |
tonyb | manjeets: PS8 got a +1 from Zuul but you said it failed almost all the jobs | 00:32 |
tonyb | manjeets: are you sure PS8 is the right one? | 00:32 |
manjeets | tonyb, there are rechecks at PS8 | 00:32 |
manjeets | it broke after it got w +1 | 00:33 |
manjeets | http://logs.openstack.org/10/576110/8/check/networking-odl-fullstack-nitrogen/f05fa85/ | 00:33 |
tonyb | Oh I see in the gate pipeline | 00:33 |
manjeets | tonyb, from ps8 recheck http://logs.openstack.org/10/576110/8/check/networking-odl-fullstack-nitrogen/f05fa85/job-output.txt.gz#_2018-07-02_11_23_58_676496 | 00:34 |
manjeets | that's why i thought i'd just cherry-pick stestr change | 00:34 |
tonyb | manjeets: stestr isn't the problem | 00:35 |
tonyb | http://logs.openstack.org/10/576110/8/gate/openstack-tox-pep8/c50d9de/job-output.txt.gz#_2018-06-27_13_26_49_857882 | 00:35 |
manjeets | tonyb, its very complicated we are looking at logs of different projects | 00:35 |
manjeets | different jobs** | 00:35 |
manjeets | not projects | 00:35 |
tonyb | manjeets: Sure but if pep8 fails then devstack will aswell | 00:36 |
manjeets | tonyb, http://logs.openstack.org/10/576110/8/gate/openstack-tox-pep8/c50d9de/job-output.txt.gz#_2018-06-27_13_26_49_858071 this looks like constraint issue | 00:37 |
manjeets | how else I add a constraint for a url | 00:37 |
manjeets | tox_install_project uses url | 00:38 |
tonyb | manjeets: Let me work through it | 00:38 |
tonyb | manjeets: 'Revert "add neutron-lbaas to global-requirements"' I5d58f036feee80a5cf9e2a252a3ff3b2b803cd37 was merged between the runs through the check and gate pipelines | 00:40 |
manjeets | tonyb, so revert a revert ? | 00:40 |
tonyb | manjeets: so I think PS8 + a small chnage to reflect that will fix you | 00:40 |
tonyb | manjeets: No that patch is correct | 00:41 |
manjeets | but stestr issue is also there in other job http://logs.openstack.org/10/576110/8/check/networking-odl-fullstack-nitrogen/f05fa85/job-output.txt.gz#_2018-07-02_11_23_58_676496 | 00:42 |
tonyb | manjeets: one problem at a time please | 00:42 |
tonyb | manjeets: I'm very sure that PS 8 is correct and it failed because it ran after I51e0902215b21abffb39d17daf780b419d55ceea was merged which was wrong. | 00:50 |
tonyb | manjeets: I think the stestr failure is a side effect of the code not being installable and therefore no tests could run so there wasn't a .testr directory | 00:52 |
tonyb | manjeets: Can you restor PS8 and try again to see what the gate says now? | 00:52 |
manjeets | tonyb, I refactored to 8 | 00:53 |
tonyb | manjeets: okay | 00:53 |
manjeets | wait it restored workflow +1 | 00:54 |
manjeets | tonyb, thanks for help, I am heading out will check gate results later | 00:54 |
manjeets | tonyb, have a good night | 00:54 |
tonyb | manjeets: I'll keep an eye on it during my day | 00:55 |
tonyb | manjeets: Have a good evening | 00:55 |
prometheanfire | tonyb: how's it going? | 01:13 |
tonyb | prometheanfire: about as well as can be expected you? | 01:14 |
prometheanfire | ok | 01:15 |
prometheanfire | tonyb: pypi mirror seem slow today? | 01:15 |
tonyb | prometheanfire: not so as I'd noticed? | 01:16 |
prometheanfire | bunch of no-distro-found stuff recently | 01:17 |
prometheanfire | that's all | 01:17 |
tonyb | prometheanfire: Hmm strange | 01:22 |
tonyb | prometheanfire: ask in #infra to see if bandersnaatch has wedged? esp if you can see $library on pypi but not in $mirror | 01:22 |
prometheanfire | k, I will if this fails one last time | 01:23 |
tonyb | prometheanfire: okay | 01:28 |
*** number80 has quit IRC | 01:45 | |
*** number80 has joined #openstack-requirements | 01:49 | |
*** hongbin has joined #openstack-requirements | 01:57 | |
*** udesale has joined #openstack-requirements | 03:24 | |
*** hongbin has quit IRC | 03:49 | |
*** udesale has quit IRC | 04:55 | |
*** udesale has joined #openstack-requirements | 04:55 | |
*** adrianreza has quit IRC | 04:58 | |
*** openstackgerrit has quit IRC | 05:10 | |
*** bauzas has quit IRC | 05:16 | |
*** robcresswell has quit IRC | 05:16 | |
*** mwhahaha has quit IRC | 05:16 | |
*** johnsom has quit IRC | 05:16 | |
*** coreycb has quit IRC | 05:16 | |
*** jmccrory has quit IRC | 05:16 | |
*** toabctl has quit IRC | 05:18 | |
*** toabctl has joined #openstack-requirements | 05:21 | |
*** bauzas has joined #openstack-requirements | 05:35 | |
*** robcresswell has joined #openstack-requirements | 05:35 | |
*** mwhahaha has joined #openstack-requirements | 05:35 | |
*** johnsom has joined #openstack-requirements | 05:35 | |
*** coreycb has joined #openstack-requirements | 05:35 | |
*** jmccrory has joined #openstack-requirements | 05:35 | |
*** florianf has joined #openstack-requirements | 06:50 | |
*** ccamacho has joined #openstack-requirements | 07:08 | |
prometheanfire | fyi, gate is wedges, infra knows | 07:33 |
*** tosky has joined #openstack-requirements | 08:06 | |
*** jpich has joined #openstack-requirements | 08:13 | |
*** dtantsur|afk is now known as dtantsur | 09:20 | |
*** dmellado has quit IRC | 10:36 | |
*** dmellado has joined #openstack-requirements | 10:42 | |
*** witek has quit IRC | 11:32 | |
*** boden has joined #openstack-requirements | 11:49 | |
*** edmondsw has joined #openstack-requirements | 12:11 | |
*** openstackgerrit has joined #openstack-requirements | 12:32 | |
openstackgerrit | Monty Taylor proposed openstack/requirements master: DNM testing pypi mirror fix https://review.openstack.org/583561 | 12:32 |
*** lbragstad has quit IRC | 13:19 | |
*** lbragstad has joined #openstack-requirements | 13:46 | |
openstackgerrit | OpenStack Proposal Bot proposed openstack/requirements master: update constraint for os-brick to new release 2.5.3 https://review.openstack.org/583585 | 14:09 |
*** udesale_ has joined #openstack-requirements | 14:26 | |
*** udesale has quit IRC | 14:27 | |
*** rpioso|afk is now known as rpioso | 15:20 | |
openstackgerrit | Martin CAMEY proposed openstack/requirements master: update constraint for python-monascaclient to new release 1.12.0 https://review.openstack.org/583281 | 15:25 |
*** lbragstad has quit IRC | 16:02 | |
*** udesale_ has quit IRC | 16:13 | |
*** udesale has joined #openstack-requirements | 16:13 | |
*** udesale has quit IRC | 16:18 | |
*** florianf has quit IRC | 16:31 | |
*** jpich has quit IRC | 16:45 | |
*** lbragstad has joined #openstack-requirements | 16:50 | |
*** dtantsur is now known as dtantsur|afk | 17:26 | |
smcginnis | prometheanfire: The google driver fix has merged. | 17:51 |
prometheanfire | woo, now for gate to unwedge | 17:51 |
smcginnis | I hope that is soon. | 17:51 |
manjeets | tonyb, hi | 18:02 |
manjeets | I think neutron-lbaas issue is gone, now python 3 requirement is killing it | 18:02 |
manjeets | I think the reason is >=1.7.2 for pylint and from upper-constraints.txt it gets 2.0.0 which has a python 3 check so I revised a patch to force 1.7.2 | 18:03 |
prometheanfire | manjeets: just update to 1.7.x (whatever the latest in that series is) | 18:06 |
manjeets | prometheanfire, you mean have == 1.7.x instead of >=1.7.x ? | 18:06 |
prometheanfire | manjeets: I don't see pylint in https://github.com/openstack/neutron-lbaas/blob/master/test-requirements.txt | 18:08 |
manjeets | http://logs.openstack.org/10/576110/11/check/openstack-tox-pep8/18e9ea4/job-output.txt.gz#_2018-07-18_01_48_11_031725 | 18:08 |
manjeets | prometheanfire, its networking-odl which had dependency on neutron-lbaas | 18:08 |
manjeets | prometheanfire, https://review.openstack.org/#/c/576110/11/test-requirements.txt | 18:09 |
manjeets | tonyb update it to 1.7.6 but for some reason it gets 2.0.0 | 18:09 |
manjeets | http://logs.openstack.org/10/576110/11/check/openstack-tox-pep8/18e9ea4/job-output.txt.gz#_2018-07-18_01_48_11_031725 | 18:09 |
manjeets | and crash saying needs python >=3.5 | 18:09 |
prometheanfire | manjeets: ah, that's because it's unconstrained, if it was ==1.7.6 that'd work | 18:10 |
prometheanfire | It should be >=1.7.6<2.0.0 | 18:10 |
prometheanfire | or something | 18:10 |
manjeets | prometheanfire, ok, i'll wait for run if this passes i'll change | 18:11 |
manjeets | and pylint has dependency on astroid, which will be next reason for same type of failure so I forced both pylint and astroid | 18:11 |
prometheanfire | just cap pylint | 18:13 |
prometheanfire | that'll fix astroid as well | 18:13 |
*** boden has quit IRC | 20:06 | |
edmondsw | u-c currently has greenlet capped at 0.4.13, so no issue... but for anyone interested in bumping that, see https://github.com/python-greenlet/greenlet/issues/136 | 20:07 |
dhellmann | prometheanfire : does the u-c list support comments? I wonder if we want edmondsw to add one with that bug report ^^ | 20:14 |
prometheanfire | dhellmann: it's auto-generated, so not sure, it's worth testing though | 20:27 |
dhellmann | prometheanfire : yeah, that's what I was afraid of | 20:28 |
prometheanfire | #startmeeting requirements | 20:28 |
openstack | Meeting started Wed Jul 18 20:28:23 2018 UTC and is due to finish in 60 minutes. The chair is prometheanfire. Information about MeetBot at http://wiki.debian.org/MeetBot. | 20:28 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 20:28 |
*** openstack changes topic to " (Meeting topic: requirements)" | 20:28 | |
openstack | The meeting name has been set to 'requirements' | 20:28 |
prometheanfire | #topic rollcall | 20:28 |
*** openstack changes topic to "rollcall (Meeting topic: requirements)" | 20:28 | |
prometheanfire | tonyb, prometheanfire, number80, dirk, coolsvap, toabctl, smcginnis, dhellmann ping | 20:28 |
prometheanfire | o/ | 20:28 |
dhellmann | o/ | 20:28 |
prometheanfire | dirk said he couldn't be here iirc | 20:28 |
smcginnis | o/ | 20:30 |
prometheanfire | gonna wait a couple min for tony if able | 20:31 |
tonyb | \o | 20:32 |
* tonyb wonders if Octonauts references would work with this group? | 20:32 | |
* dhellmann googles octonauts | 20:33 | |
* prometheanfire googles octonauts | 20:33 | |
prometheanfire | that the switch thing? | 20:33 |
tonyb | that was pretty much what I thought :( | 20:33 |
tonyb | It's a kids TV show | 20:33 |
smcginnis | I'm well past that stage. :) | 20:33 |
tonyb | anyway let's do this meeting thing ;P | 20:33 |
dhellmann | so, nothing to do with october | 20:33 |
prometheanfire | #topic Any controversies in the Queue? | 20:34 |
*** openstack changes topic to "Any controversies in the Queue? (Meeting topic: requirements)" | 20:34 | |
smcginnis | Is it being broken controversial? | 20:34 |
prometheanfire | lol | 20:34 |
dhellmann | is the pypi mirror still causing trouble, or is there something else? | 20:34 |
prometheanfire | just the mirror, ya | 20:34 |
tonyb | hehe I dont' see any controversies, but clearly it's broken and we wanted to talk about post releases | 20:35 |
prometheanfire | ok | 20:35 |
prometheanfire | #topic brokenness | 20:35 |
*** openstack changes topic to "brokenness (Meeting topic: requirements)" | 20:35 | |
tonyb | prometheanfire: are infra on it? or should I monitor that during my day | 20:35 |
prometheanfire | they are | 20:35 |
smcginnis | There's a patch in gate right now to fix it. | 20:35 |
tonyb | \o/ | 20:35 |
smcginnis | Or at least work around it for now. | 20:36 |
prometheanfire | just pinged mordred about it | 20:36 |
prometheanfire | still bad | 20:36 |
smcginnis | Oh, looks like the one they hoped would get around it merged: https://review.openstack.org/#/c/583571/ | 20:36 |
tonyb | Ahh okay, that kind of broken I thought it was just the normal bindersnatch thing | 20:36 |
prometheanfire | anyway, once it's fixed we can update the uc on networkx and the two google libs | 20:36 |
tonyb | is there a 30sec summary of the problem? | 20:37 |
prometheanfire | they ran out of space | 20:37 |
tonyb | Oh okay that's well less that 30secs | 20:37 |
prometheanfire | said it'll be fixed in 15 minutes or so | 20:37 |
smcginnis | Taskflow uploads ~500m of packages nightly. Mirroring locally got too big. | 20:37 |
smcginnis | Darn storage. | 20:37 |
dhellmann | I guess we need a bandersnatch->swift converter | 20:37 |
smcginnis | I saw some discussion of that. | 20:37 |
prometheanfire | 500M for taskflow? | 20:37 |
smcginnis | prometheanfire: Yep | 20:37 |
tonyb | smcginnis: Really? what are they uploading? | 20:38 |
prometheanfire | wow | 20:38 |
smcginnis | The world? | 20:38 |
dhellmann | what on earth | 20:38 |
smcginnis | I guess some of the ML stuff is pretty big for some reason. | 20:38 |
tonyb | dhellmann: I dont' think so I think that the mirrors are staycing on AFS it's only logs that are moving | 20:38 |
dhellmann | tonyb : yeah, I meant for the future | 20:38 |
prometheanfire | anyway, moving on then | 20:38 |
prometheanfire | #topic freeze | 20:38 |
*** openstack changes topic to "freeze (Meeting topic: requirements)" | 20:39 | |
dhellmann | smcginnis : tensorflow? | 20:39 |
prometheanfire | I'll need to find more mr freeze puns, maybe rewatch batman & robin | 20:39 |
smcginnis | Oh, sorry. Yes, tensorflow. | 20:39 |
prometheanfire | the things I suffer for you | 20:39 |
dhellmann | ok, whew. | 20:39 |
tonyb | smcginnis, dhellmann: Oh that makes away mmore sense! | 20:39 |
smcginnis | prometheanfire: :D | 20:39 |
dhellmann | prometheanfire : I hear they're rebooting the iceman comics | 20:40 |
tonyb | the earth stops shaking ;P | 20:40 |
prometheanfire | dhellmann: :D | 20:40 |
smcginnis | Heh, sorry. That would be really bad if taskflow was that big. | 20:40 |
prometheanfire | this freeze should be easier because of the per-project reqs | 20:40 |
dhellmann | well, we could at least do something about that :-) | 20:40 |
tonyb | With the freeze and pre-project requirements we need to think a little about minimum bumping | 20:40 |
prometheanfire | this is still the process https://etherpad.openstack.org/p/requirements-cycle-process | 20:41 |
tonyb | in that say (bad example) oslo.privsep adds a new API/constant today and it merges and is released next week at what point can python-swiftclient bump the minimum to require that (for them)? | 20:41 |
tonyb | what about say $clientlibrary that is pulled into python-openstackclient? | 20:42 |
dhellmann | as long as the u-c list isn't changed, does it matter? | 20:42 |
prometheanfire | they could bump it immediately, as long as their min is not over our UC | 20:42 |
prometheanfire | packagers would need to look at swifts lower-constraints to find swifts min | 20:43 |
tonyb | dhellmann: I'm not sure, which is why I'm asking ;P I feel like if python-openstackclient took bumped a minimum that kinda of implies that they'd like a release and uc bump | 20:44 |
tonyb | which I guess will all come out in the exception proecess | 20:44 |
tonyb | I just wanted to discuss it ahead of time | 20:44 |
dhellmann | sure | 20:44 |
prometheanfire | so you want to make sure that their reqs are in any given release? | 20:44 |
dhellmann | I'm also making sure I'm not missing something :-) | 20:44 |
tonyb | prometheanfire: Yup and we have dhellmann build tool to make life slightly easier for packagers to work that out | 20:45 |
dhellmann | I do think if we end up needing a release of a library for a bug fix, we need to coordinate the u-c update ahead of time. But I think we generally do that in this period of the cycle anyway, right? | 20:45 |
prometheanfire | tonyb: ya, you talking about the global-lc.txt builder? | 20:45 |
dhellmann | we don't want to have a case where we release a library and then don't allow the u-c update, because then we have a thing out in the wild that we're not using in our own tests | 20:45 |
tonyb | prometheanfire: Yup | 20:45 |
prometheanfire | ok, anything else for now about the freeze? | 20:46 |
tonyb | dhellmann: Yup I agree and I guess without the bot updates a release is less impactful in that only projects that are actually impacted by the bug need to update | 20:46 |
tonyb | and if a project works that out after the fact the fixed version shoudl be available | 20:47 |
dhellmann | tonyb : ideally we wouldn't update minimums just for bug fixes, but yeah | 20:47 |
tonyb | dhellmann: true, but it does happen esp when a bug fix changes an API (by say adding a new kwarg) | 20:48 |
prometheanfire | yarp | 20:48 |
dhellmann | tonyb : sure | 20:48 |
tonyb | it may be I'm over thinking ia and worrying too much due to not enough coffee | 20:48 |
dhellmann | nah, it's good to review this stuff | 20:49 |
prometheanfire | ya, just in case | 20:49 |
dhellmann | maybe we should write the reasoning down so we don't have to think so hard next time :-) | 20:49 |
prometheanfire | dhellmann: formalizing the release process for reqs would be nice | 20:50 |
tonyb | dhellmann: good plan | 20:50 |
prometheanfire | turning https://etherpad.openstack.org/p/requirements-cycle-process more official | 20:50 |
dhellmann | yeah, that made a big difference in our confidence on the release team | 20:50 |
tonyb | prometheanfire: want to add something to the end of that etherpad | 20:50 |
prometheanfire | tonyb: go ahead? | 20:50 |
dhellmann | we have a rst file in the releases repo now; that etherpad could move over to the requirements repo eventually | 20:50 |
tonyb | prometheanfire: +1 having some process docs in repo (like releases) would be good | 20:50 |
tonyb | dhellmann: snap :_ | 20:50 |
smcginnis | That might be a good place for that. | 20:51 |
dhellmann | maybe that's a project for stein | 20:51 |
tonyb | prometheanfire: I mean *can you* add something to the end of that etherpad (or PROCESS.rst) | 20:51 |
prometheanfire | tonyb: of course, it's just a review away | 20:52 |
tonyb | dhellmann: I feel like we can start now. it has no material impact on the release | 20:52 |
tonyb | prometheanfire: cool | 20:52 |
dhellmann | oh, sure, I just meant that we could be deliberate about updating it throughout the cycle at different points where the rules change or whatever | 20:52 |
prometheanfire | #topic open floor | 20:52 |
*** openstack changes topic to "open floor (Meeting topic: requirements)" | 20:52 | |
tonyb | so we have 8mins left do we want to discuss post releases in general? | 20:52 |
tonyb | and pyldap specifically? | 20:53 |
dhellmann | do we have any topics lined up to discuss at the ptg? | 20:53 |
dhellmann | oh, sure, that's more important, let's do that | 20:53 |
prometheanfire | tonyb: sure | 20:53 |
prometheanfire | dhellmann: I think I'll start thinking about ptg next week (after freeze) | 20:53 |
dhellmann | makes sense | 20:53 |
* tonyb wont be at the PTG but if y'all want to hangouts me into anything I can be available pening TZs | 20:53 | |
dhellmann | aw! | 20:53 |
prometheanfire | tonyb: but you'll miss the choo choo puting you to sleep | 20:54 |
smcginnis | That's unfortunate. | 20:54 |
tonyb | dhellmann, smcginnis: goes for rleases to | 20:54 |
prometheanfire | tonyb: so, post release? | 20:54 |
dhellmann | yeah, we'll keep that in mind | 20:54 |
tonyb | so post releases | 20:54 |
smcginnis | tonyb: Thanks. If we have some topics we'll try to find a convenient time. | 20:54 |
dhellmann | so, what's the deal with post releases? why are we worried about them? | 20:54 |
tonyb | I think they got lumped with pre releases and theer was some unreasonable FUD about accepting them | 20:54 |
dhellmann | ah, ok | 20:55 |
tonyb | I think we shoudl at a minimum evealuate each, if not just accept them | 20:55 |
dhellmann | iirc, the only reason we don't like pre-releases is that pip needs special instructions to install them | 20:55 |
dhellmann | does that apply to post releases? | 20:55 |
prometheanfire | oh, those .post releases | 20:55 |
tonyb | and pyldap is a trivial one to accept as it's litterally the same code as 3.0.0 | 20:55 |
prometheanfire | I think we should just accept them | 20:55 |
prometheanfire | we don't need to disable pre-releases because they are already disabled by default | 20:56 |
prometheanfire | that would make my review not needed | 20:56 |
tonyb | dhellmann: I thought there was more it it than that in that there is a perception that they're more risky | 20:56 |
dhellmann | I guess I don't understand that perception | 20:56 |
tonyb | put perhaps that's linked to pre releases of $major bumps | 20:57 |
dhellmann | if the same package was tagged with a new version number we wouldn't even behaving the conversation, right? | 20:57 |
prometheanfire | doesn't debian have something like that? | 20:57 |
prometheanfire | 1.2.3-2 | 20:57 |
prometheanfire | gentoo has 1.2.3-r2 for instance | 20:57 |
prometheanfire | it's the same concept | 20:57 |
tonyb | dhellmann: that's true | 20:57 |
prometheanfire | this is a question of if we allow revision bumps, I can't see a reason why | 20:57 |
prometheanfire | s/why/why not | 20:57 |
dhellmann | perhaps we should treat them like any other update, and let the test jobs evaluate them on a case-by-case basis | 20:57 |
tonyb | I guess some of it came from before we had the cross-project gateing we have now | 20:58 |
dhellmann | hmm | 20:58 |
prometheanfire | so, everyone fine with just allowing them? if so I'll drop my review | 20:58 |
dhellmann | +1 for allowing them | 20:58 |
tonyb | prometheanfire: for varying values of fine ;P | 20:58 |
dhellmann | at least until things blow up in our face, I guess :-) | 20:59 |
tonyb | but yeah I think I'm good with it | 20:59 |
prometheanfire | sgtm | 20:59 |
tonyb | dhellmann: at least a u-c (partial) revert is easy | 20:59 |
dhellmann | yeah | 20:59 |
tonyb | .pre/.post releases for EVERYBODY ;p | 21:00 |
prometheanfire | tonyb: anything else? | 21:00 |
tonyb | prometheanfire: I don't think so | 21:00 |
prometheanfire | tonyb: I don't think pre-releases are good, but those have to be manually proposed anyway | 21:00 |
tonyb | prometheanfire: not all of them | 21:00 |
prometheanfire | ok, going to endmeeting | 21:00 |
prometheanfire | #endmeeting | 21:00 |
*** openstack changes topic to "OpenStack Requirements - IRC meetngs on Wednesdays @ 07:00 UTC in here in #openstack-requirements - See agenda @ http://tinyurl.com/h44ryuw - IRC channel is *LOGGED* @ http://tinyurl.com/j38rk24" | 21:00 | |
openstack | Meeting ended Wed Jul 18 21:00:54 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 21:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/requirements/2018/requirements.2018-07-18-20.28.html | 21:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/requirements/2018/requirements.2018-07-18-20.28.txt | 21:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/requirements/2018/requirements.2018-07-18-20.28.log.html | 21:00 |
prometheanfire | tonyb: they don't? | 21:01 |
tonyb | prometheanfire: the bot will propose them sometimes | 21:01 |
tonyb | prometheanfire: and I don't know why | 21:01 |
prometheanfire | ah, ok | 21:01 |
tonyb | prometheanfire: I've seen the bot suggest them | 21:01 |
tonyb | manjeets: I'll look after breakfast | 21:08 |
prometheanfire | rechecked allthethings | 21:29 |
*** edmondsw has quit IRC | 21:54 | |
*** lbragstad has quit IRC | 22:29 | |
tonyb | manjeets: Ohh I see what's going on, yeah we need to use pylint== not pylint>= which you've done | 23:13 |
tonyb | manjeets: if you can get one neutron-stable-core to +2 it I can +2+W it. | 23:14 |
prometheanfire | tonyb: >= can work with a cap as well | 23:17 |
tonyb | prometheanfire: Sure but that seems more problematic than use using == | 23:19 |
tonyb | if we had pylint in u-c then sure we shoudl use >= but we don't | 23:19 |
prometheanfire | meh, your choice | 23:19 |
*** tosky has quit IRC | 23:20 | |
tonyb | prometheanfire: I thought we'd worked out that caps are bad | 23:20 |
tonyb | prometheanfire: anyway it isn't worth discussin anymore | 23:20 |
prometheanfire | we did, but we don't do anything with pylint, so that's your problem :P | 23:20 |
*** rpioso is now known as rpioso|afk | 23:48 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!