Pulp 3:
-
Query for the upcoming release
-
https://pulp.plan.io/projects/pulp_rpm/issues?query_id=149
-
Copy API docs
-
Maybe we can publish them after the release? +1
-
PR reviews
-
“Relative_path” problem
-
https://www.redhat.com/archives/pulp-dev/2020-April/msg00000.html
-
Need to come back to it and bump the thread
-
Will be discussed at the pulpcore meeting
-
Import/export
-
Main path works, tech-preview in 3.3
-
pulp_file/pulp_rpm happy-path available
-
Docs in progress
-
Setting up handoff mtg w/katello next week
-
Public invite to list
-
Dennis volunteered to manage accepts
-
Invite QE folks
-
Katello timeline and deliverables
-
Ask if anything is unclear
-
3.3.0 release
-
Monday or Tuesday
-
Daniel to take care of the release
-
Testing publish task
-
Easy to test using the REST API:
https://github.com/pulp/pulp_rpm/blob/master/pulp_rpm/tests/functional/api/test_publish.py#L347
-
Problem: how to test publish task directly? How to emulate a synced
repo? (Unit and Functional tests run on different places on CI)
- Brian to write a proposal to solve this type of testing problems
Pulp 2:
-
Both items from last week needs to be taken care of
-
for the RPM migration to Pulp 3
-
https://pulp.plan.io/issues/6354
-
https://pulp.plan.io/issues/6355
-
CentOS directory KS structure is no longer RH compatible
-
https://pulp.plan.io/issues/6470
-
the same problem in Pulp3
- Dennis to test more and file an issue if needed
Open PRs:
-
https://github.com/pulp/pulp_rpm/pulls
Triage:
-
Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
Tests:
- Pulp 3 https://pulp.plan.io/projects/pulp_rpm/issues?query_id=153
_______________________________________________
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev
