Do I understand correctly, that the suggestion is not to have versioned api at all but document some conventions/expectations between pulpcore releases and plugin API?
I wonder if there is still a benefit to keep it as a separate package and as-is. I understand that now we need to release both at the same time, however we are in active development now and when things are more stable we might benefit from having it separate. It sounds like we are back to pulp2 case, where we would need to release the core if any plugin api changes are needed, just this time we organised code better. Since we have a meetup next week, does it make sense to discuss it there? Plans on what we want or expect to support and what kind of changes we foresee in this area? Where the plugin api versioning will benefit us? I see many +1s, so it might not worth a discussion and maybe I'm the only one who is concerned. Tanya On Thu, Oct 17, 2019 at 5:58 PM David Davis <[email protected]> wrote: > Done. > > David > > > On Thu, Oct 17, 2019 at 11:49 AM Brian Bouterse <[email protected]> > wrote: > >> Yes the issue is here: https://pulp.plan.io/issues/5580 >> >> If someone else can groom, I'm +1 to adding to sprint and labelling 3.0 >> blocker. >> >> On Thu, Oct 17, 2019 at 11:01 AM David Davis <[email protected]> >> wrote: >> >>> Any chance we open an issue and get this on the sprint so that we can >>> maybe release this change in RC8? >>> >>> David >>> >>> >>> On Thu, Oct 17, 2019 at 10:49 AM Mike DePaulo <[email protected]> >>> wrote: >>> >>>> On Thu, Oct 17, 2019 at 10:25 AM Brian Bouterse <[email protected]> >>>> wrote: >>>> >>>>> I put some responses inline. I'm interested in what you think. >>>>> >>>>> On Thu, Oct 17, 2019 at 10:10 AM Mike DePaulo <[email protected]> >>>>> wrote: >>>>> >>>>>> Q: Will both pulpcore & pulpcore-plugin be published on PyPI as 1 >>>>>> package, or as 2? >>>>>> >>>>> I had imagined it would be 1. Users wouldn't be able to receive >>>>> pulpcore.plugin except through an install of the pulpcore==3.y.z itself. >>>>> >>>> >>>> Great, that makes things easier for users' manual installs, and easier >>>> for containers/packaging. >>>> >>>> >>>>>> If so, how will you pip install from a pip VCS URL >>>>>> <https://pip.pypa.io/en/stable/reference/pip_install/#id32>? With >>>>>> #egg=pulpcore , and then #egg=pulpcore-plugin ? >>>>>> >>>>> You wouldn't perform the second one anymore. >>>>> >>>> >>>> Great, that makes things easier for users' manual installs, and easier >>>> for containers/packaging. >>>> >>>> -Mike >>>> >>>>> >>>>> >>>>>> -Mike >>>>>> >>>>>> On Thu, Oct 17, 2019 at 5:17 AM Simon Baatz <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> +1 >>>>>>> >>>>>>> On Wed, Oct 16, 2019 at 03:50:54PM -0400, Mike DePaulo wrote: >>>>>>> > +1. >>>>>>> > >>>>>>> > On Wed, Oct 16, 2019 at 3:26 PM Pavel Picka <[1] >>>>>>> [email protected]> >>>>>>> > wrote: >>>>>>> > >>>>>>> > +1 >>>>>>> > >>>>>>> > On Wed, Oct 16, 2019 at 9:23 PM Dana Walker <[2] >>>>>>> [email protected]> >>>>>>> > wrote: >>>>>>> > >>>>>>> > +1, more straightforward >>>>>>> > >>>>>>> > Dana Walker >>>>>>> > >>>>>>> > She / Her / Hers >>>>>>> > >>>>>>> > Software Engineer, Pulp Project >>>>>>> > >>>>>>> > [3]Red Hat >>>>>>> > >>>>>>> > [4][email protected] >>>>>>> > [5][Logo-RedHat-Email.png] >>>>>>> > >>>>>>> > On Wed, Oct 16, 2019 at 2:55 PM David Davis <[6] >>>>>>> [email protected]> >>>>>>> > wrote: >>>>>>> > >>>>>>> > +1 >>>>>>> > David >>>>>>> > >>>>>>> > On Wed, Oct 16, 2019 at 2:38 PM Daniel Alley <[7] >>>>>>> [email protected]> >>>>>>> > wrote: >>>>>>> > >>>>>>> > Very Large +1 >>>>>>> > >>>>>>> > On Wed, Oct 16, 2019 at 2:10 PM Brian Bouterse <[8] >>>>>>> [email protected]> >>>>>>> > wrote: >>>>>>> > >>>>>>> > Having just released RC7, there are a variety of problems we are >>>>>>> > dealing with as a result of having pulpcore and pulpcore-plugin >>>>>>> being >>>>>>> > in separate repos. @daviddavis and I were talking, and we want >>>>>>> to ask >>>>>>> > for feedback on merging the code from pulpcore-plugin into >>>>>>> pulpcore. >>>>>>> > I wrote this up as an issue here: [9] >>>>>>> https://pulp.plan.io/issues/5580 >>>>>>> > Thanks! >>>>>>> > Brian >>>>>>> > >>>>>>> > _______________________________________________ >>>>>>> > Pulp-dev mailing list >>>>>>> > [10][email protected] >>>>>>> > [11]https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>> > >>>>>>> > _______________________________________________ >>>>>>> > Pulp-dev mailing list >>>>>>> > [12][email protected] >>>>>>> > [13]https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>> > >>>>>>> > _______________________________________________ >>>>>>> > Pulp-dev mailing list >>>>>>> > [14][email protected] >>>>>>> > [15]https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>> > >>>>>>> > _______________________________________________ >>>>>>> > Pulp-dev mailing list >>>>>>> > [16][email protected] >>>>>>> > [17]https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>> > >>>>>>> > -- >>>>>>> > >>>>>>> > Pavel Picka >>>>>>> > Red Hat >>>>>>> > >>>>>>> > _______________________________________________ >>>>>>> > Pulp-dev mailing list >>>>>>> > [18][email protected] >>>>>>> > [19]https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>> > >>>>>>> > -- >>>>>>> > >>>>>>> > Mike DePaulo >>>>>>> > >>>>>>> > He / Him / His >>>>>>> > >>>>>>> > Service Reliability Engineer, Pulp >>>>>>> > >>>>>>> > [20]Red Hat >>>>>>> > >>>>>>> > IM: mikedep333 >>>>>>> > >>>>>>> > GPG: 51745404 >>>>>>> > [21][Logo-RedHat-Email.png] >>>>>>> > >>>>>>> > References >>>>>>> > >>>>>>> > 1. mailto:[email protected] >>>>>>> > 2. mailto:[email protected] >>>>>>> > 3. https://www.redhat.com/ >>>>>>> > 4. mailto:[email protected] >>>>>>> > 5. https://www.redhat.com/ >>>>>>> > 6. mailto:[email protected] >>>>>>> > 7. mailto:[email protected] >>>>>>> > 8. mailto:[email protected] >>>>>>> > 9. https://pulp.plan.io/issues/5580 >>>>>>> > 10. mailto:[email protected] >>>>>>> > 11. https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>> > 12. mailto:[email protected] >>>>>>> > 13. https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>> > 14. mailto:[email protected] >>>>>>> > 15. https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>> > 16. mailto:[email protected] >>>>>>> > 17. https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>> > 18. mailto:[email protected] >>>>>>> > 19. https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>> > 20. https://www.redhat.com/ >>>>>>> > 21. https://www.redhat.com/ >>>>>>> >>>>>>> > _______________________________________________ >>>>>>> > Pulp-dev mailing list >>>>>>> > [email protected] >>>>>>> > https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> 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 >>>>>> [email protected] >>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>> >>>>> >>>> >>>> -- >>>> >>>> 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 >>>> [email protected] >>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>> >>> _______________________________________________ > Pulp-dev mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-dev >
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
