Jun 03, 2020 -
Triage - https://pulp.plan.io/projects/pulp/issues?query_id=157 - Should released issues receive the pulpcore milestone? - The concern is: what happens if pulp_installer needs to release asynchronously of pulpcore due to bugfix for example - If pulp_installer needs to be re-released to fix a bug, the release number should be incremented and the same milestone as the original release be used. - Displays which plugins are compatible with the latest pulpcore: - Repo - https://github.com/fao89/pdc - Asciinema - https://asciinema.org/a/335533 - Task written and added to sprint: https://pulp.plan.io/issues/6904 - Galaxy dev install - https://github.com/fao89/galaxy_ng_prerequisites/blob/master/tasks/main.yml - https://pulp.plan.io/issues/6696 - Commented and closed because installer does collect static - Should we support source install with git url? - Wrote refactor task <https://pulp.plan.io/issues/6903> to merge galaxy_ng_prerequisites into pulp_installer: - Prereqs Epic - https://pulp.plan.io/issues/6797 - Adding to sprint @fao89 to start into this work - Installer support of install-by-rpms-instead-of-pypi - https://pulp.plan.io/issues/6793 - TLS support for the installer planning - https://pulp.plan.io/issues/6331 Action Items: - [all] learn more about pulp_database x geerling.postgres - Schedule a meeting to clean up redmine issues -- Mike DePaulo He / Him / His Service Reliability Engineer, Pulp Red Hat <https://www.redhat.com/> IM: mikedep333 GPG: 51745404 [image: image.png] <https://www.redhat.com/>
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
