[Pulp-dev] Pulp Installers Team Meeting Minutes 2021-08-04

Mike DePaulo mikedep333 at redhat.com
Wed Aug 11 15:23:46 UTC 2021

## Aug 4 Agenda
* The SELinux Epic
    * https://pulp.plan.io/issues/97
* I keep on running into situations that would be easier to resolve if this
were implemented. https://pulp.plan.io/issues/8701
    * Team busy, discuss next week
* db key fix needed by 3.15 - https://pulp.plan.io/issues/9200
    * david - I'm happy to test this out if it can be done by thurs/friday
    * fao89 assigned
* minor branch model
    * How to handle upgrades?
        * Current model for plugins: `upgrade` or `version`. They are
mutually exclusive.
            * `upgrade`: `pip install --upgrade plugin`
            * `version`: `pip install plugin==version`
        * `update` could be mutually exclusive with `version`, but it could
also be combined with it to be like `~=version`
            * `update`: "determine current-version", then `pip install
            * `version`: `pip install plugin==version`
            * `update` + `version`: `pip install --upgrade plugin~=version`
(but this may not be feasible due to the Ansible' `pip` module's
        * How to handle upgrades?
            * Option 1: Make users specify the new x.y.z `version`, within
the new y-stream (currently implemented)
            * Option 2: `upgrade` option. (currently implemented)
            * Option 3: `update` + `version`
            * These options are not mutually exclusive. Users could have
multiple ways. But Option 2 is insufficient.


Mike DePaulo

He / Him / His

Service Reliability Engineer, Pulp

Red Hat <https://www.redhat.com/>

IM: mikedep333

GPG: 51745404
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20210811/c2322ad2/attachment.htm>

More information about the Pulp-dev mailing list