Bug 2005139

Summary: major versioned latest compose symlink
Product: Red Hat Enterprise Linux 9 Reporter: Carl George 🤠 <carl>
Component: distributionAssignee: RHEL Program Management <pm-rhel>
Status: MODIFIED --- QA Contact: Release Test Team <release-test-team>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: bstinson, jwboyer, tdawson
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-13 15:58:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Carl George 🤠 2021-09-16 21:47:08 UTC
Description of problem:
We currently have a latest-CentOS-Stream symlink in https://composes.stream.centos.org/production/ pointing to the latest compose.  Without an equivalent symlink including the major version (e.g. latest-CentOS-Stream-9), it's not clear what will happen when a new major version exists, or how people can reference the latest compose for each major version.


Additional info:
I'm working on code changes to fedscm_admin to support epel9-next.  Currently that tool blocks epelX and epelX-next branch requests based on packages that are in RHEL.  I'd like to have it check CentOS Stream compose metadata to block epelX-next branch requests.  I'm proceeding with that using the current latest-CentOS-Stream symlink, but in the future it needs to be switched to something that limits to a major version.

Comment 1 Troy Dawson 2022-11-02 14:29:55 UTC
This is just a quick ping to say that this is being discussed.
There are a couple of proposals for a solution and we're seeing which is best for the build environment.

Comment 2 Troy Dawson 2022-12-07 15:44:38 UTC
After much testing and probing of ODCS we have determined that we will have the following structure.

NOTE:  This is not implemented yet.  I do not have an estimate of when it will be finished.

The new structure will be

stream-{8,9,10}/{test,development,production}/latest-CentOS-Stream/

An example is currently available
https://composes.stream.centos.org/stream-9/test/latest-CentOS-Stream/

The base {test,development,production} directories will become symlinks and point to the latest stream release.
Thus production/ will point to stream-9/production for now, and when CentOS Stream 10 is released, production/ will then point to stream-10/production

Again, this is not implemented yet.  It should be before February 2023, but how much before, we currently don't know.

Comment 4 Troy Dawson 2023-02-14 14:17:45 UTC
The CentOS Stream 8 stuff is there, but it currently isn't being used in production yet.  But if you wanted to start getting scripts pointing to it you can.
https://composes.stream.centos.org/stream-8/development/
https://composes.stream.centos.org/stream-8/production/

Comment 6 Carl George 🤠 2023-03-15 20:32:22 UTC
I'd like to keep this bug open until this is completed.  After it's completed I need to submit changes to fedpkg and fedscm-admin for epel9/epel10 branch checks, and it would be nice to have this bug being closed as the reminder to go do that.

Comment 8 Troy Dawson 2023-03-15 20:47:14 UTC
Sounds good.
I expect we'll get stream-9 to be transitioned before we have to deal with stream-10.  Otherwise it will be a bit of a mess.
But I'll keep this open until we get everything in place.

Comment 10 Troy Dawson 2023-08-16 13:18:27 UTC
I've updated the stale date.
I don't think this will be completely fixed/done until CentOS Stream 10 starts getting composes built.  That won't happen for 6 months to a year.  So I've extended the stale date.