## 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
plugin~=current-version`
* `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
limitations.)
* 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
<https://www.redhat.com/>
_______________________________________________
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev
