-
Sub-task
-
Resolution: Done
-
Minor
-
None
-
None
-
False
-
None
-
False
-
NEW
-
ppc64le, s390x
-
NEW
-
Sprint 223
Problem statement: During the 4.10-rc cycle, the P CI team discovered that RCs were released sometimes without a nightly ID, this makes it very difficult for the CI team to determine which CI run is related to a particular RC build.
Per Yaakov's explanation: "While promoting from a nightly is a normal way of creating a stable release, ART has the ability to cherry-pick fixes. in order to minimise the changes needed to fix late-breaking blocker bugs, that's what they've been doing. once GA occurs, then the following stable release is likely to go back to being a promoted nightly, and so on."
Need: We need to determine a strategy of how we can address RC releases or zstream releases without a nightly ID.