August 5, 2020
Pulp
-
Core
-
Still on target for 3.6 on August 11th
-
Will change the bindings methods-argument-order
-
RPM
-
Avoiding collection name collisions for advisories
-
Package environment copy fix
-
https://pulp.plan.io/issues/7248
-
In progress: mirror + optimize = empty repo version
-
https://pulp.plan.io/issues/7228
-
import/export remaining entities, kickstarts aiming for 3.6 as well
-
Migration
-
0.2.0b7 is out with the correct pulpcore version pinned
-
Many performance fixes
-
Depending on how clean cherry-picks are might end up being
compatible with pulpcore 3.5 only
-
Fixes for distribution tree migration are under review
-
Fix migration of treeinfo file (without a . in the name)
-
Migrate all lazy catalog entries so they are not affecting re-runs.
-
Ansible
-
0.2.0 GA will be released as compat release with 3.6
-
General
-
Backport requests can use the “Backport” tracker in the issue type to
request
-
https://github.com/pulp/pulpcore/pull/816/files#diff-45ef661bb3358093f1fe193290cf4d8bR86
Katello
-
Working on finalizing 3.16 with yum on pulp3 for fresh installs, no yum
migration
-
3.16 will have pulpcore-3.4, pulp_rpm-3.5
-
3.17 branching ‘soon’, will build against 3.6 pulpcore and supported
plugins
-
Going to work to upgrade nightly to pulpcore 3.5, should we wait for 3.6?
-
Tested 3.6(nightly) bindings
-
Multi-repo dep solving
-
Fixes for package env changes (now copy them all)
David
_______________________________________________
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev
