[releng] Issue #7763: define and implement retention policy for nightly composes
sharkcz reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Right now we have only last 14 days of the nightly composes. Which makes it impossible to
compare current compose with an old one to see what changed (mainly functionally). The
polocy could be time based (like keep 1 compose per week for 4 weeks preceding the 14
days, then keep 1 per month, until previous GA). Or it can be based on the openqa testing
and keep composes "nominated for further testing". Or something else.
One of the reason for this request is https://bugzilla.redhat.com/show_bug.cgi?id=1623547
where I'm almost sure I had a F-29 nightly compose behaving sanely on s390x in the
past, but have nothing I could compare with the current state.
* When do you need this? (YYYY/MM/DD)
soon
* When is this no longer needed or useful? (YYYY/MM/DD)
never
* If we cannot complete your request, what is the impact?
Difficult to find out what changed (functionally) in the composes as the previous compose
is the GA compose of the last release. AFAIK it's almost impossible to recreate an old
compose from a given date on demand.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7763