Priority items (outside of planned milestones/releases) Priority list of items which will be needed soon but which are not aligned to any milestone or release 9% 11 issues (0 closed — 11 open) Related issues Issue #6410: Package_group contains relations of packages from all the repos package_group is in Actions Story #4552: As a user, zchunk metadata is supported Actions Story #4812: As a user, I can publish a Yum repository that works with repo_gpgcheck=1 (Signed Repositories) Actions Story #5356: RpmPublication should include a repo file that clients can use to configure yum/dnf Actions Story #5367: As a user, I can have a sync option that retains the latest N packages of the same name Actions Story #5402: As a developer, Package content allows ORDER_BY in postgres based on EVR comparisons Actions Story #5433: As a user, I can do a one-shot upload of custom repository metadata Actions Story #5740: As a user, advisory collection names are unique within an advisory Actions Story #5950: Add database support for comparing EVRs Actions Story #6225: As a user, I can sync from a mirror list feed Actions
Pulp 3.x RPM (Katello release) A release with all the features needed for Katello to switch to Pulp 3 RPM plugin. 65% 36 issues (19 closed — 17 open) Related issues Issue #6018: As a user, I have an API for copying content between repositories Actions Issue #6295: Package in a different repo does not get added to package list on Module Actions Issue #6303: If same content is provided by 2 remotes, resync raises ValueError: Path is duplicated Actions Issue #6312: Upload Content workflow doc broken Actions Issue #6322: Parsing kickstarts' '.treeinfo' fails against opensuse repository Actions Task #3824: Analyze repository version creation performance for pulp_rpm Actions Task #4873: Add models for future use with modularity Actions Task #5158: Analyze existing opensource projects to potentially be used for applicability calculation Actions Task #5171: Extend UpdateRecord model to support modular advisory Actions Task #5201: Create the model(s) for distribution trees as Content models Actions Task #5934: Implement API for applicability Actions Task #5935: Model and build relations between Advisory and Package Actions Task #5936: Build additional fixtures to represent all cases needed to test applicability Actions Task #5937: Write tests for checking applicability correctness Actions Task #5938: Add swagger docs for applicability API Actions Task #5939: Benchmark performance and optimize applicability Actions Task #5940: Implement backend initial calculation of applicability Actions Task #6332: Create documentation for the copy API Actions Story #4445: As a user, RPMs are published in Packages/ and sorted alphabetically Actions Story #4458: As a user, I can configure which checksum algorithm to use when creating metadata Actions Story #4761: As a user, I have RPM dependency solving Actions Story #4762: [Epic] As a user, I can copy content Actions Story #5112: [Epic] As a user, I can manage auxiliary content types Actions Story #5113: Sync optimizations Actions Story #5114: [Epic] Publish features Actions Story #5117: [Epic] As a user, I can export RPM repositories Actions Story #5172: As a user, I can sync modular content Actions Story #5202: As a user, I can sync distribution trees Actions Story #5206: As a user, I can publish a distribution tree Actions Story #5429: As a user, I can manage custom repository metadata Actions Story #5493: As a user, I can publish repository with modular content Actions Story #5739: As a user, advisory version is considered at conflict resolution time Actions Story #5829: Add support for opensuse UpdateRecord Actions Story #6019: As a user, I can specify content to be copied by the content's pulp_href Actions Story #6055: As a user, my sync is not operational if there are no changes Actions Story #6353: As a user, I can mirror RPM repository content and metadata Actions
.
.
.