Re: [Pulp-dev] 2.20.0 Release Schedule

A 2.20.0 dev freeze is scheduled for tomorrow, June 25, 2019 @ 23:00 UTC. Please make sure everything which should be in 2.20.0 is merged by then, including bug fixes. Thank you! On Tue, Jun 18, 2019 at 3:33 PM Tatiana Tereshchenko wrote: > Just a reminder that a 2.20 dev freeze is approaching

Re: [Pulp-dev] black

Per our PUP voting guidelines, PUP-8 has passed and been merged. I filed the required issues in an epic[0]. Thank you to everyone that voted and participated in the discussion. [0] https://pulp.plan.io/issues/5019 David On Mon, Jun 24, 2019 at 11:28 AM Ina Panova wrote: > -0. Fully agree

[Pulp-dev] Mtg notes, Pulp3.0 GA/backlog discussions

Hey folks, There was a discussion around Pulp3.0, deciding how to triage "must be in" vs...otherwise, and dealing with the non-prioritized backlog. You can find a braindump/minutes here : https://etherpad.net/p/Pulp_3.0%2C_3.1_backlog_meeting The TL;DR that came out of the meeting was: -

[Pulp-dev] Sprint 55 Meeting Minutes

Not a whole lot to add in addition to *https://pulp.plan.io/projects/pulp/wiki/Sprint_Plans * *21-Jun-2019* *Action Items:* - rchan: new, assigned, post - moved during sprint planning - rchan: Clear Sprint Candidate

Re: [Pulp-dev] uniqueness constraints within a repository version

I have a design in mind for solving this problem: 1. Remove POST to RepositoryVersion (no general add/remove endpoint). 2. Add an endpoint to kick off an add/remove task, namespaced by plugin. ie `POST pulp/api/v3/docker/add-remove/` This view can be provided to all plugins by the plugin

Re: [Pulp-dev] black

-0. Fully agree with Tanya's 3rd point of observation. Regards, Ina Panova Senior 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 Wed, Jun 19, 2019 at 5:22 PM Austin Macdonald wrote: > +1. I like