| *** tosky has quit IRC | 00:02 | |
| *** edmondsw has joined #openstack-requirements | 00:38 | |
| *** edmondsw has quit IRC | 00:42 | |
| *** openstackgerrit has joined #openstack-requirements | 00:50 | |
| openstackgerrit | Tony Breeds proposed openstack/requirements master: Support cloning one freeze to multiple https://review.openstack.org/580241 | 00:50 |
|---|---|---|
| prometheanfire | dhellmann: why did we stop syncing other branches? | 00:52 |
| tonyb | prometheanfire: (missing contect) Do you mean why did we disable the constraints bot onf stable/* | 00:59 |
| tonyb | Oh I see, we've disabled the requirements bot on all branches | 00:59 |
| prometheanfire | yes | 00:59 |
| tonyb | Interesting | 00:59 |
| prometheanfire | yes | 00:59 |
| *** edmondsw has joined #openstack-requirements | 02:26 | |
| openstackgerrit | Tony Breeds proposed openstack/requirements master: Add openshift to global-requirements https://review.openstack.org/580093 | 02:29 |
| *** edmondsw has quit IRC | 02:30 | |
| openstackgerrit | Merged openstack/requirements stable/queens: update constraint for tripleo-common to new release 8.6.3 https://review.openstack.org/580457 | 03:53 |
| openstackgerrit | Merged openstack/requirements stable/queens: update constraint for instack-undercloud to new release 8.4.3 https://review.openstack.org/580458 | 04:12 |
| *** edmondsw has joined #openstack-requirements | 04:14 | |
| *** edmondsw has quit IRC | 04:18 | |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/requirements master: Updated from generate-constraints https://review.openstack.org/580792 | 06:30 |
| openstackgerrit | Merged openstack/requirements stable/queens: update constraint for os-net-config to new release 8.4.3 https://review.openstack.org/580459 | 07:37 |
| *** vpickard_ has quit IRC | 11:56 | |
| *** vpickard_ has joined #openstack-requirements | 11:56 | |
| *** tosky has joined #openstack-requirements | 12:29 | |
| *** vpickard_ has quit IRC | 13:26 | |
| *** vpickard_ has joined #openstack-requirements | 13:29 | |
| *** vpickard_ has quit IRC | 14:20 | |
| *** tosky has quit IRC | 15:50 | |
| dhellmann | prometheanfire, tonyb : I thought we wanted to stop syncing requirements on stable branches because we didn't want those changing anyway. | 16:05 |
| *** hwoarang has quit IRC | 16:20 | |
| *** hwoarang has joined #openstack-requirements | 16:23 | |
| *** hwoarang has quit IRC | 16:23 | |
| *** hwoarang has joined #openstack-requirements | 16:23 | |
| *** edmondsw has joined #openstack-requirements | 16:51 | |
| prometheanfire | dhellmann: why don't we want those changes? | 16:54 |
| *** edmondsw has quit IRC | 16:56 | |
| *** tosky has joined #openstack-requirements | 17:56 | |
| dhellmann | we don't want people changing the dependencies on stable branches, right? | 18:37 |
| dhellmann | just the constraints? | 18:37 |
| *** edmondsw has joined #openstack-requirements | 18:39 | |
| prometheanfire | dhellmann: we still want to mask known bad don't we? | 18:43 |
| dhellmann | sure, but we don't have to copy that setting into all of the branches because we can control it with constraints | 18:44 |
| dhellmann | s/branches/repos/ | 18:44 |
| *** edmondsw has quit IRC | 18:44 | |
| prometheanfire | but it isn't just for tests that we mask things, otherwise we'd only care about constraints | 18:45 |
| prometheanfire | I check for requirements updates per project when I package things | 18:45 |
| dhellmann | what behavior are you asking to restore? | 18:47 |
| prometheanfire | sync changes from global-reqs to project reqs for queens and below (where that behavior previously was) | 18:47 |
| dhellmann | why do we want to treat the old branches as special in that particular way, though? | 18:48 |
| dhellmann | we won't be doing it for rocky, right? | 18:48 |
| dhellmann | so at some point you're no longer going to be able to rely on that behavior | 18:48 |
| dhellmann | how about a tool that looks at the project list and g-r list and merges the exclusions | 18:50 |
| dhellmann | that would let you have the info you want without requiring a bunch of other people to deal with all of those sync patches | 18:50 |
| dhellmann | sort of like the tool for merging the lower constraints files | 18:50 |
| prometheanfire | I thought the change in behavior was for rocky+ | 18:51 |
| prometheanfire | how is pip install for a lib going to know about the exclusion? | 18:52 |
| dhellmann | it will have the constraint list | 18:54 |
| dhellmann | we support pip using the constraint list and distros support their system packages | 18:54 |
| dhellmann | those are the 2 basic use cases | 18:54 |
| dhellmann | project teams are free to be very detailed with exclusions in the dependencies of their libraries, of course, but the most important things to me are (a) having a good set of things to test with and (b) expressing what that list of versions is | 18:55 |
| prometheanfire | we don't care about consumers? | 18:56 |
| dhellmann | having accurate minimum bounds is also important, but lower on the list | 18:56 |
| dhellmann | which consumers? | 18:56 |
| prometheanfire | Raising effective minimums is only acceptable during Phase I, and only due to security issues. | 18:57 |
| prometheanfire | which means we need to support pushing that out, at least for queens- | 18:57 |
| dhellmann | I don't think we should be raising minimums at all on stable branches. They are *minimums* not the list of things we expect people to use. | 18:58 |
| dhellmann | we may need to do some work to write up the goals and mission of the team, because I think we have some conflicting priorities if not conflicting goals | 18:58 |
| prometheanfire | possibly | 18:59 |
| dhellmann | maybe we can do that over the next week or so, during regular hours | 18:59 |
| dhellmann | I'm only online today because I'm upgrading my dev box :-) | 18:59 |
| prometheanfire | the current stable policy supports raising effective minimums, meaning, either changing >= or adding != | 18:59 |
| prometheanfire | dhellmann: yep, didn't expect a quick response | 18:59 |
| dhellmann | ok, supporting and requiring are different, so maybe that's where we're having different expectations | 19:00 |
| prometheanfire | supporting means it's an available option, meaning we need to support pushing it out (imo) :P | 19:01 |
| dhellmann | I guess if you want to turn the job back on for stable branches earlier than rocky I won't get in the way. I think it's unnecessary and produces busy work for little value, though. The information it conveys is available from other sources if we look at the system as a whole instead of looking at 1 package at a time. | 19:02 |
| prometheanfire | true, I guess the question is if we need to deliver that information and how | 19:03 |
| dhellmann | yes, we should probably have another discussion about exactly what information we can, want to, and need to deliver | 19:05 |
| dhellmann | my upgrade is done, so I'm going to drop back offline. maybe we can talk more this week. | 19:05 |
| prometheanfire | cya | 19:21 |
| *** edmondsw has joined #openstack-requirements | 20:27 | |
| *** edmondsw has quit IRC | 20:32 | |
| *** edmondsw has joined #openstack-requirements | 22:15 | |
| *** edmondsw has quit IRC | 22:20 | |
| *** tosky has quit IRC | 23:20 | |
| openstackgerrit | Tony Breeds proposed openstack/requirements master: Add openshift to global-requirements https://review.openstack.org/580093 | 23:41 |
| openstackgerrit | Tony Breeds proposed openstack/requirements master: Updated from generate-constraints https://review.openstack.org/580792 | 23:51 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!