Pulp 2:

   -

   1770940 <https://bugzilla.redhat.com/show_bug.cgi?id=1770940> - figured
   out why there’s a performance difference, now need to figure out what to do
   about it
   -

   Katello calls differ (no clone distributor is used), Pulp does publish
   in the same way

   -

   https://github.com/pulp/pulp_rpm/pull/1558 sync perf improvement ( from
   CDT)
   -

      Ipanova will follow up ( next year)

Pulp 3:

   -

   Copy API
   -

      https://pulp.plan.io/issues/5344
      -

      discussed use cases, expect a follow-up email on pulp-dev list

      -

   Cherry picks next week
   -

      In the event of an emergency (eg Katello encounters a major blocker)
      is there someone who can cherry pick to the 3.0 branch? Or do we
just wait
      until Jan?
      -

      Yes, there will be pulp-committers available next week if needed
      -

   Release status
   -

      Will start after meeting
      -

   Applicability - draft design doc is out, feedback is needed
   -

   Is #5841 <https://pulp.plan.io/issues/5841> (Document how to install
   libcomps and dependencies) needed for GA?
   -

      https://github.com/pulp/pulp_rpm/pull/1570 - Needs cherry-pick
      -

   All 3 of Mike’s RPM-related Ansible installer issues are on QA/MODIFIED


Open PRs:

   -

   https://github.com/pulp/pulp_rpm/pulls


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
_______________________________________________
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Reply via email to