On 3 July 2015 at 21:25, Dave Walker wrote:
> On 3 July 2015 at 10:17, Robert Collins wrote:
>> On 3 July 2015 at 21:01, Thierry Carrez wrote:
>
>>> - Does that (or should that) also affect stable/kilo and stable/juno ?
>>> (there is no upper-constraints there)
>>
>> No, and since the disruptio
On 3 July 2015 at 10:17, Robert Collins wrote:
> On 3 July 2015 at 21:01, Thierry Carrez wrote:
>> - Does that (or should that) also affect stable/kilo and stable/juno ?
>> (there is no upper-constraints there)
>
> No, and since the disruption of a new pbr and associated minimum
> versions throu
Robert Collins wrote:
> On 3 July 2015 at 21:01, Thierry Carrez wrote:
> [...]
>> - Does that (or should that) also affect stable/kilo and stable/juno ?
>> (there is no upper-constraints there)
>
> No, and since the disruption of a new pbr and associated minimum
> versions throughout stable would
On 3 July 2015 at 21:01, Thierry Carrez wrote:
> Robert Collins wrote:
>> I want to give an update on
>> http://specs.openstack.org/openstack/openstack-specs/specs/requirements-management.html
>> - we've just passed a critical milestone there, and this affects how
>> everyone updates requirements.
Robert Collins wrote:
> I want to give an update on
> http://specs.openstack.org/openstack/openstack-specs/specs/requirements-management.html
> - we've just passed a critical milestone there, and this affects how
> everyone updates requirements.
>
> As of a few minutes ago devstack-gate landed the
I want to give an update on
http://specs.openstack.org/openstack/openstack-specs/specs/requirements-management.html
- we've just passed a critical milestone there, and this affects how
everyone updates requirements.
As of a few minutes ago devstack-gate landed the change to set
USE_CONSTRAINTS=Tru
