Excerpts from Dmitry Tantsur's message of 2017-01-17 18:48:59 +0100:
> On 01/17/2017 04:55 PM, Doug Hellmann wrote:
> > In this review for the ironic-inspector-client newton release [1], Alan
> > pointed out that the new release was pulled into our master requirements
> > because the constraints bo
Excerpts from Jeremy Stanley's message of 2017-01-17 18:15:59 +:
> On 2017-01-17 18:48:59 +0100 (+0100), Dmitry Tantsur wrote:
> [...]
> > In theory there is nothing wrong with this, as 1.10 is the latest
> > release indeed. In practice, that means pulling in something with
> > stable/newton re
From: Jeremy Stanley
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Tuesday, January 17, 2017 at 10:15 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [release][requirements] disable con
On 2017-01-17 18:48:59 +0100 (+0100), Dmitry Tantsur wrote:
[...]
> In theory there is nothing wrong with this, as 1.10 is the latest
> release indeed. In practice, that means pulling in something with
> stable/newton requirements into master, which is concerning, I
> agree.
[...]
I don't really s
On 01/17/2017 04:55 PM, Doug Hellmann wrote:
In this review for the ironic-inspector-client newton release [1], Alan
pointed out that the new release was pulled into our master requirements
because the constraints bot saw it as a newer release. That doesn't seem
like something we want to have hap
In this review for the ironic-inspector-client newton release [1], Alan
pointed out that the new release was pulled into our master requirements
because the constraints bot saw it as a newer release. That doesn't seem
like something we want to have happen, as a general case. Should we
update the bo
