On 2015-07-14 07:03:34 -0400 (-0400), Sean Dague wrote: > I just saw this Nova review come in - > https://review.openstack.org/#/c/200908 > > Why are we merging 2.6 requirements for projects that don't support 2.6? > That seems potentially confusing to end users that now think the project > does, because there are still references in the code.
We could likely consider treating 2.6+2.7-supporting vs 2.7-only (and 2.7+3.4-supporting? and 2.6+2.7+3.4?) repos differently where requirements sync and enforcement are concerned, but a first step for that would involve coming up with and maintaining a list of which repos have support on which branches for which Python versions. We don't have such a thing today as far as I'm aware, as it's merely an emergent property based on a combination of factors in zuul's layout file (the names of 2.6-based jobs, which repos run them, and the branches on which they're allowed to run). -- Jeremy Stanley __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
