[Pulp-dev] Pulpcore meeting notes
David Davis
daviddavis at redhat.com
Tue Nov 24 20:45:29 UTC 2020
Ah, ok. thank you.
David
On Tue, Nov 24, 2020 at 3:40 PM Tanya Tereshchenko <ttereshc at redhat.com>
wrote:
> Just because you were not present, I carried over your items which were
> not marked as done and the ones we were not sure about the next steps.
> Feel free to adjust them as you see it.
> We didn't assign anything new to you while you were away :)
>
> Tanya
>
> On Tue, Nov 24, 2020 at 8:26 PM David Davis <daviddavis at redhat.com> wrote:
>
>> Thanks for taking notes and sorry I couldn't be at the meeting. Can you
>> explain more about the action item to give updates on the tagging story? I
>> was planning on following up on the mailing lists with updates since I
>> don't think the feature will be specific to pulpcore.
>>
>> As for the automatic merge PR (https://github.com/pulp/pulp-ci/pull/737),
>> I wasn't planning on carrying forward an AI for it. I don't have any time
>> to address in the near future but I'm happy to hand it off to someone else
>> if they're interested.
>>
>> David
>>
>>
>> On Tue, Nov 24, 2020 at 12:43 PM Tanya Tereshchenko <ttereshc at redhat.com>
>> wrote:
>>
>>> Previous action items
>>>
>>> - [david] To send out last call for feedback before merging
>>> https://github.com/pulp/pulp-ci/pull/737
>>> - Hold off until after Github Actions move
>>> - [fao89] look at driving forward release automation.
>>> - Automate post-release steps (branching, bumping to dev
>>> versions, updating template config, etc)
>>> - https://pulp.plan.io/issues/7817 (needs grooming, please
>>> provide feedback)
>>> - https://pulp.plan.io/issues/7818 (needs grooming)
>>> - [david] a Pulp query that shows issues for pulpcore (filters out
>>> installer, operator, etc)
>>> - Done: https://pulp.plan.io/projects/pulp/issues?query_id=166
>>> - [david] move django fips repo to pulp
>>> - Done: https://github.com/pulp/django/
>>> - [david] notify pulp-list mailing list of 3.9 release schedule
>>> - [ttereshc] file a task to have task management code manage working
>>> dir
>>> - [david] to start on tagging planning
>>> - https://pulp.plan.io/issues/7127
>>> - Started. Met with David Newswanger yesterday.
>>> - Hope to have draft design by next week.
>>>
>>> <https://hackmd.io/XfI9DxymSAu6UJnblh7prQ?both#Topics>Topics
>>>
>>> - two feature plans pending for pulp-dev discussion
>>> - parallelizing orphan cleanup while avoiding runtime
>>> errors(ipanova)
>>> - started writing down a proposal
>>> - alternate content sources(bmbouter)
>>> - needs feedback
>>> - meeting with Katello next week
>>> - https://pulp.plan.io/issues/7832
>>> - RBAC pulpcore issue
>>> - https://pulp.plan.io/issues/7710
>>> - 3.9 blocker
>>> - how to remove a plugin, including the relevant data in the db
>>> - pulpcore-manager command?
>>> - checks if the plugin is installed
>>> - if not, drops all <plugin_app_label>_* tables?
>>> - use cases
>>> - migration plugin is the one which everyone would want to
>>> remove eventually
>>> - it’s needed for katello
>>> - if no general solution is available, we will make some
>>> custom one for the migration plugin only
>>> - incompatible plugins, one might want to remove one
>>> - ttereshc to create a task
>>> - Validate existing group on pulpcore?
>>> -
>>> https://github.com/ansible/galaxy_ng/pull/572/files#diff-6b9632eb49cb924f729282743cdac58a36f7625974fef12da2ea7b946ac19866R32
>>> - pulpcore uses Django Group model, not a custom one, so likely
>>> no need
>>> -
>>> https://github.com/django/django/blob/7af8f4127397279d19ef7c7899e93018274e2f9b/django/contrib/auth/models.py#L109
>>> - 3.10 release
>>> - Tentatively planned for Jan 8? due to holidays. Feedback
>>> welcome.
>>> - probably too early, maybe end of January?
>>> - Galaxy NG will likely need a release of pulpcore at the
>>> end of Jan’21
>>> - Conference driven release
>>> - Decide after 3.9 release
>>> - Needs volunteer to release
>>> - An assumption in the ArtifactSaver stage that a d_artifact always
>>> has a remote.
>>> -
>>> https://github.com/pulp/pulpcore/blob/master/pulpcore/plugin/stages/artifact_stages.py#L297
>>> - Is it intentional?
>>> - Not intentional
>>> - move the check on line 300 couple of lines up
>>> - Currently causes issues for the migration
>>> - https://pulp.plan.io/issues/7876
>>>
>>> <https://hackmd.io/XfI9DxymSAu6UJnblh7prQ?both#Action-items>Action items
>>>
>>> - [david] To send out last call for feedback before merging
>>> https://github.com/pulp/pulp-ci/pull/737
>>> - Hold off until after Github Actions move
>>> - [fao89] look at driving forward release automation.
>>> - Automate post-release steps (branching, bumping to dev
>>> versions, updating template config, etc)
>>> - https://pulp.plan.io/issues/7817 (needs grooming, please
>>> provide feedback)
>>> - https://pulp.plan.io/issues/7818 (needs grooming)
>>> - [ttereshc] to file a task to implement plugin removal
>>> - [fao89] to figure out the use case for this fix
>>> https://github.com/ansible/galaxy_ng/pull/572/files#diff-6b9632eb49cb924f729282743cdac58a36f7625974fef12da2ea7b946ac19866R32
>>> - [david] updates on tagging planning
>>> https://pulp.plan.io/issues/7127
>>>
>>> _______________________________________________
>>> Pulp-dev mailing list
>>> Pulp-dev at redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20201124/062b16e1/attachment.htm>
More information about the Pulp-dev
mailing list