<div dir="ltr">## Aug 4 Agenda<br>* The SELinux Epic<br>    * <a href="https://pulp.plan.io/issues/97">https://pulp.plan.io/issues/97</a><br>* I keep on running into situations that would be easier to resolve if this were implemented. <a href="https://pulp.plan.io/issues/8701">https://pulp.plan.io/issues/8701</a><br>    * Team busy, discuss next week<br>* db key fix needed by 3.15 - <a href="https://pulp.plan.io/issues/9200">https://pulp.plan.io/issues/9200</a><br>    * david - I'm happy to test this out if it can be done by thurs/friday<br>    * fao89 assigned<br>* minor branch model<br>    * How to handle upgrades?<br>        * Current model for plugins: `upgrade` or `version`. They are mutually exclusive.<br>            * `upgrade`: `pip install --upgrade plugin`<br>            * `version`: `pip install plugin==version`<br>        * `update` could be mutually exclusive with `version`, but it could also be combined with it to be like `~=version`<br>            * `update`: "determine current-version", then `pip install plugin~=current-version`<br>            * `version`: `pip install plugin==version`<br>            * `update` + `version`: `pip install --upgrade plugin~=version` (but this may not be feasible due to the Ansible' `pip` module's limitations.)<br>        * How to handle upgrades?<br>            * Option 1: Make users specify the new x.y.z `version`, within the new y-stream (currently implemented)<br>            * Option 2: `upgrade` option. (currently implemented)<br>            * Option 3: `update` + `version`<br>            * These options are not mutually exclusive. Users could have multiple ways. But Option 2 is insufficient.<br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:capitalize"><span>Mike</span> <span>DePaulo</span><span style="text-transform:uppercase;color:rgb(170,170,170);margin:0px"></span></p><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:12px;margin:0px 0px 4px;text-transform:capitalize">He / Him / His</p><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:12px;margin:0px;text-transform:capitalize"><span>Service Reliability Engineer, Pulp</span></p><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;margin:0px 0px 4px;font-size:12px"><a href="https://www.redhat.com/" style="color:rgb(0,136,206);margin:0px" target="_blank">Red Hat<span></span></a></p><div style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:medium;margin-bottom:4px"></div><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;margin:0px;font-size:12px"><span>IM: <span>mikedep333</span></span></p><p style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:12px;margin:0px"><span>GPG: 51745404</span></p><div style="color:rgb(0,0,0);font-family:RedHatText,sans-serif;font-size:medium;margin-top:12px"><table border="0"><tbody><tr><td width="100px"><a href="https://www.redhat.com/" target="_blank"><img src="https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png" width="90" height="auto"></a></td></tr></tbody></table></div></div></div></div>