As mentioned in https://mailweb.openeuler.org/hyperkitty/list/dev@openeuler.org/thread/WQ3MZ... , we are adding openEuler support in mock upstream. When I propose to add openEuler 20.03 SP3 as a mock configuration. Looks like there are some different ideas from upstream. https://github.com/rpm-software-management/mock/pull/965 Currently, we maintain the openEuler LTS version with a separate repo url, that means each version (even it's the SP version) has their own lifecycle. From the upstream view, if only the major version (such as 20.03) is exposed to users, it might have more friendly UX. There are a potential solution: Only the 20.03 is exposed, and we update the repo url to 20.03 SP3 url but keep 20.03 exposing upstream, just like our openeuler/openeuler docker images (20.03 always point to the latest SP version <https://github.com/openeuler-mirror/openeuler-docker-images/blob/84b9c266518f7dd0046d414ce39d53f928bab09c/.github/workflows/basic-image-push.yml#L29>) did. But I think it might be a generic question about how the upstream community can use openEuler friendly, so I just raised topic in here: *1. Why does each SP version have their own lifecycle? What was our initial consideration?* *2. Should we consider putting all sp3 updates into base version (such as 20.03 LTS) updates in future?* Regards, Yikun