Open Stack

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 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 bot to avoid changing constraints for the things we release
> > ourselves? That will let us more carefully manage which updates go into
> > which branches, since the release jobs update the constraints files
> > as part of the release process.
> 
> 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.
> 
> However, not updating upper constraints at all seems overly strict too. This 
> will essentially cause people to do it manually. Maybe we should just make sure 
> that for our projects we only take releases from an appropriate branch?

Well, the release process submits those patches automatically (updating
only the constraint setting for the newly released library). So no more
manual work would be needed.

Doug

> 
> >
> > Doug
> >
> > [1] https://review.openstack.org/#/c/398401/
> >
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>