Comment 4 for bug 1928190

With respect to https://review.opendev.org/c/openstack/requirements/+/790091 I think it needs to be reverted for now; based on [1] (thanks Rabi for pointers) we need to keep tripleo-common in global requirements because it is listed in requirements.txt of some of the (tripleo) projects that are listed in projects.txt [2].

We then need to discuss and decide about leaving the requirements contract (i.e. trying to re-land 790091 but together with the rest of the required changes).

My initial impression is that this is not a good idea as it shields us against projects making incompatible changes in their requirements.txt.

[1] https://docs.openstack.org/project-team-guide/dependency-management.html#enforcement-in-projects
[2] https://github.com/openstack/requirements/blob/ce19462764940a4ce99dae4ac2ec7a004c68e9a4/projects.txt#L245-L249