It could continue to cause confusion around installation best practices as well as headaches if the user moves to either an ODH or RHODS managed installation of the operator from the OperatorHub version
Reason to continue publishing upstream CFO:
users who are uninterested in the rest of the ODH/RHODS stack can continue to install the operator independently
Neutral Note:
allows for versioning that is independent of ODH/RHODS releases
Reason for avoiding publishing of upstream CFO:
Reason to continue publishing upstream CFO:
Neutral Note: