if we won't pin pulpcore we'll keep receiving such reports as #4317. +1 to option1 -------- Regards,
Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Jan 17, 2019 at 2:06 PM Tatiana Tereshchenko <ttere...@redhat.com> wrote: > With more plugins going Beta and with frequent releases of pulpcore and > pulpcore-plugin an issue with dependencies version showed up: > - plugin requires pulpcore-plugin == 0.1.0bX > - pulpcore-plugin 0.1.0bX requires pulpcore >= 3.0.0bY > - at some point pulpcore introduces backward incompatible changes and the > newest pulpcore is incompatible with the old pulpcore-plugin. E.g. > https://pulp.plan.io/issues/4317 > > It would be less of a problem when pulpcore goes GA but till then it is > not nice user experience. > > Options to solve the issue: > 1. Pin pulpcore with every pulpcore-plugin release > 2. Pin pulpcore directly in a plugin > 3. Don't do anything, we are in Beta, it will be fine when pulpcore is > GA, semver will keep us from introducing backward incompatible changes in > the Y or Z releases. > 4. anything else? > > As a side note, we already have an issue with having multiple plugins > installed if they require different pulpcore-plugin versions, so pinning > pulpcore wouldn't introduce a new problem. Again this should be solved > when we go GA, in my opinion. > > Any thoughts or concerns are welcome. > > Thank you, > Tanya > > _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
