[Pulp-dev] Katello/Pulp-Community Integration meeting minutes

[Grant Gainey]

Our second open integration meeting. Good questions, good discussion! We've
decided to hold these monthly, adjusting as we go. Next meeting is 1000 EDT
01-JUN - anyone who's interested in attending, let me know at
ggainey at redhat.com and I'll add you to the invite!

Happy reading,
G

https://hackmd.io/@pulp/pulp-deb-katello-integration

## 2021-05-04 1000-1031
### Attendees: quba42, mbucher, ggainey, jsherrill
### Regrets:
### Agenda:
* Taking stock: pulp_deb updates are now planned for Katello 4.0.1 and
3.18.4 (complete for devel)
    * Remaining open [packaging PRs](
https://github.com/theforeman/foreman-packaging/pull/6587) are red.
        * re-running job should fix
    * [rubygem-katello.spec changes](
https://github.com/theforeman/foreman-packaging/blob/3a0e355a86196383225b9f3d08d0852c7c501dd9/packages/katello/rubygem-katello/rubygem-katello.spec#L59)
are still missing.
        * will happen "automatically" for release (but not nightly)
* When will the next pulpcore version branch be created for
pulpcore-packaging?
    * please invite/notify quba42 next time we do this so he can learn How
It All Works
    * can we add pulp-dev@ , foreman-dev@ to the email to build-team
requesting next branch?
    * AI: jsherrill to add to wiki, heads-up to Evgeni
* Is Katello 3.18 the last version on which 2to3 migrations are possible?
    * correct - by the time you're on katello-4.0, you're done with 2to3
* What about pulp_deb "cassette test" coverage?
    * AI: jsherril to sched 30 min "How to do VCR tests" pair-programming
exercise
* Are there plans for Katello to adopt the new (pulpcore 3.13) Pulp
"autopublish" feature?
    * katello will prob not take advantage of this
* Can version level dependencies from Katello to Pulp components be made
explicit?
    * Goal: A new package in a pulpcore-packaging repo should never break
existing releases.
    * Consider a multi node scenario where Pulp is on a different node from
Katello.
    * This is a hard problem, and we need to think about how we can solve it
    * Multiple stakeholders on multiple schedules with multiple needs makes
everything Fun!
### Action Items:
* AI: jsherrill to update release-wiki with a note to notify pulp-dev@ when
starting a release-branch
* AI: jsherrill to schedule a 30-min "How to VCR" exercise w/ quba42,
mbucher
* AI: ggainey to schedule next meeting for beginning of June [done, 01-JUN]
* AI: ggainey to send minutes to pulp-dev@

-- 
Grant Gainey
Principal Software Engineer, Red Hat System Management Engineering
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20210504/79655124/attachment.htm>