On Thu, 2017-06-01 at 11:18 -0400, Bihan Zhang wrote: > I've been documenting the plugin API semver strategy for 3.0 but I've noticed > that the plugins > were recently moved from plugin/pulp/plugin to platform/pulp/plugin > > My understanding was that we would have separate packages for plugin and > platform to enforce the > separate semantic versioning, instead of just having documentation on the > plugin version supported > by platform. > > I think the correct workflow is for a plugin writer would denote in their > spec file (or setup.py) > what pulpcore-plugin versions are supported, and on installation the package > manager can pull in > the correct pulpcore-plugin package with the correct platform dependency. > > > I wanted to check that this was everyone else's understanding too.
+1 to separating these as packages. Having a package version to depend on should help enforce the plugin api version.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
