|
Kenn Hussey in terms of semver, in my interpretation, updating the dependency in 5.1 would not violate semver (http://semver.org/#what-should-i-do-if-i-update-my-own-dependencies-without-changing-the-public-api) as the ultimate result in PDB would not be a change to public api.
However, I'm still trying to tease apart the implications of doing or not doing this change for the ecosystem. Currently, FOSS PDB specifies a dependency on puppet < 5.0.0 which I think means that users can't upgrade to Puppet 5 on their FOSS PDB/MOM unless we make this change - PDB 5.0 can be installed only with Puppet Agent 4.10.x or earlier.
PE PDB does not specify a versioned dependency on puppet-agent - it's free-floating. So I think we'd be OK there - ie if we do the update in PE PDB 5.1 (presumably meaning the new dependency would go live in Irving). I believe the first thing to be upgraded in PE is the agent, so when PDB is installed/upgraded later, the dependency on Puppet 5.0.0 would already be satisfied. Alternatively for PE we could leave it as-is, ie not specify any versioned requirement at all, and just rely on users taking supported upgrade paths to ensure the right packages are co-installed - thought that feels risky if we're depending on API changes across the projects. Thoughts Joshua Partlow?
|