Hey @jvanek,

just to confirm, I wanted to double-check on the naming convention since, we are using epel10.0 tags for this, do you want to change the tag nomenclature to el10.0-openjdk?

Here's an example what I had in my mind:

koji add-tag ep10.0-openjdk --parent=epel10.0-build --arches=x86_64,aarch64,ppc64le,s390x
koji add-target el10.0-openjdk el10.0-openjdk
koji regen-repo el10.0-openjdk

CC: @carlgeorge, just looping you in

hi! Thanx for heads up. What the .0 will be for? I had noticed it in the builds, and was surprised ny its existence. I doubt that epel will ever follow the rhel's major_minor of each major. Epel is just rolling? On contrary, if you would create jsut el10-openjdk it would mean that you would need to edit thsi tag?

I doubt that epel will ever follow the rhel's major_minor of each major.

That is precisely what is happening in EPEL 10. We don't have this fully documented yet, mainly because EPEL 10 hasn't officially launched yet, but it is described in detail in the original proposal discussion thread. There is also a more up to date summary from the CentOS Connect conference earlier this year.

https://discussion.fedoraproject.org/t/epel-10-proposal/44304

https://youtu.be/mUoI0rqWfmY

Epel is just rolling?

EPEL has never been rolling (and by policy doesn't allow rolling packages), but it has been major version only until now.

On contrary, if you would create jsut el10-openjdk it would mean that you would need to edit thsi tag?

I'm not sure exactly what the best approach for openjdk would be. We had a similar question come up in #12334 for the openh264 tags. We decided that the best approach in that case will be to follow the minor versions. We've built in a step to the work-in-progress EPEL SOP to clone the epel10.0-openh264 tag to create an epel10.1-openh264 tag when the time comes. Specifically, we'll run koji clone-tag --all --latest-only epel10.0-openh264 epel10.1-openh264, which will duplicate the configs, groups, package lists, and builds. Do you think that would work for the way you're using the openjdk tags? I saw your description in one of the issues you linked as a "permanent protected sidetag". I would lean towards handling this the same way as openh264 and using minor versions, just to avoid doing something non-standard.

In those cases, I think these works, CC: @jvanek

koji add-tag el10.0-openjdk --parent=epel10.0-build --arches=x86_64,aarch64,ppc64le,s390x
koji add-target el10.0-openjdk el10.0-openjdk
koji regen-repo el10.0-openjdk