-
Previous AIs:
-
core/3.24 releasing TODAY
-
core/3.25 #soon - mid/end of May?
- 3.25.0 blockers Milestone · GitHub
- django-4.2
- psycopg3
- any deprecation warnings? fix em now!
- next breaking-release: core/3.40
- discussion
- packaging?
- where do plugins look to find dperecation-warnings?
- quba42 to ask in OpenFloor
- AI: [ggainey] is there a list of core-releases we backport stuff to?
- write this down somewhere
- eg, “what releases does katello depend on”
-
pulp_deb release: Pulp_deb 2.20.2 has been released!
- bindings change implied?
- makes katello-packaging harder
- serializer-change - almost certainly yes
- can this be ready for katello/4.9 release?
- should be possible
- quba42 to investigate/do/poke katello if more info needed
-
SLES advisory export/import problem
-
Working with the Katello upload implementation:
- https://github.com/Katello/katello/blob/master/app/lib/actions/pulp3/orchestration/repository/upload_content.rb
- Katello is open to using the
repository parameter on content endpoints instead of separately calling the modify API after creating the content.
- If the upload workflow needs to change for plugins that implement “create or retireve” logic on the Pulp side, there are two options:
- A flag in the existing workflow (if the two workflows are not very different)
- A separate workflow that is called for some plugins
- The goal should be to ultimately move all plugins to the new workflow and move “create or retrieve” logic from Katello to Pulp.
