[puppet] Artificially inflated dependencies in metadata.json of all modules
zigo at debian.org
Thu Mar 25 16:24:55 UTC 2021
Each time there's a new release, all of the modules are getting a new
set of lower bounds for:
I just did a quick check and this really doesn't make sense. For
example, for going from 18.2.0 to 18.3.0, there's no breakage of the API
that would require a bump of version in all modules.
So, could we please stop this non-sense and restore some kind of sanity
in our dependency management ? FYI, I'm expressing these in the packaged
version of the puppet modules, and it increase complexity for no reasons.
A lower bound of a dependency should be increased *only* when really
mandatory (ie: a backward compatibility breakage, a change in the API,
Thomas Goirand (zigo)
More information about the openstack-discuss