Open Stack

On 2019-03-26 10:01:25 -0500 (-0500), Ghanshyam Mann wrote:
[...]
> if links modification is in any library (something on code side)
> then, should not we release that lib and bump the min version(low
> constraint)? otherwise, it fails when project gate
> jobs/installation install that lib with an older version which use
> old url?

About the only places I can imagine this could be necessary is
deployment projects which perform deployment from source and default
to retrieving source code from our Git service by default. If any of
those projects are using classic git protocol over 9418/tcp instead
of HTTP/HTTPS then they will likely want to perform some point
releases prior to April 19. I strongly doubt any of these are
tracked in global requirements or constraints files, so there
shouldn't be knock-on effects.

> I was reviewing openstack-dev/hacking changes [1]  when this
> question strikes me but hacking change is just in tests so we are
> ok there.
> 
> [1] https://review.openstack.org/#/c/646379/
[...]

Yeah, as you say, this one isn't really an example of the possible
class of problem you're describing.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190326/8e223eb9/attachment.sig>