Just curious, but I assume that for an async plugin release that would
imply zero changes to the exposed APIs and only fixes to the underlying
code?
As a consumer of pulp, we install pulp-server not individual plugins. If a
plugin changes it's exposed interface (ie. API) then I'd expect a bump on
On Tue, Jun 19, 2018 at 10:54 AM, Ina Panova wrote:
> Dennis,
> thank you for sending out the summary of our meeting.
>
> Just to highlight and check the overall understanding - there will be one
> repository per Y pulp release which might contain multiple Z and Y plugin
> version releases.
>
Dennis,
thank you for sending out the summary of our meeting.
Just to highlight and check the overall understanding - there will be one
repository per Y pulp release which might contain multiple Z and Y plugin
version releases.
Correct me if i am wrong.
What would be our next steps in terms of
I've written up stories for this work, which I've marked as sprint
candidates. I'd like to get them groomed this week if possible.
Testing: https://pulp.plan.io/issues/3773
Documentation: https://pulp.plan.io/issues/3772
On Mon, Jun 18, 2018 at 3:48 PM, Dennis Kliban wrote:
> +1
>
> On Mon,
