On Fri, Feb 28, 2020 at 10:40 AM Brian Bouterse <bmbou...@redhat.com> wrote:
> tl;dr: Have your plugin's setup.py only declare a minimum compatibility > requirement with pulpcore, e.g. 'pulpcore>3.1' instead of what we typically > do now 'pulpcore>3.1,<3.3'. > > # motivation > > When pulpcore releases a y-stream release it's master branch iterates to > the next y-version. So for the 3.2 release master became 3.3.0.dev. When > other plugins contain upper version limits this change breaks many plugins. > > > # solution > > Don't declare a maximum version on 'master'. Do declare a maximum version > when you release though, to ensure users don't receive the next pulpcore > y-release which could contain backwards incompatible changes. > > Other ideas or suggestions are welcome. This is just my recommendation. > > -Brian > I agree with this change. I think it will save more hassle than it creates. -- Mike DePaulo He / Him / His Service Reliability Engineer, Pulp Red Hat <https://www.redhat.com/> IM: mikedep333 GPG: 51745404 <https://www.redhat.com/>
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
