kellin reported a new issue against the project: `pungi-fedora` that you are following:
The way we rsync composes today is a one-liner bash script that is not very durable and
requires that a release engineer babysit it through the entire four hour rsync process.
I am going to make this more durable, however, it will also slightly change our process
behind the scenes.
Today if a process works or is DOOMED after a full run it is assigned an RC release
number. (EG: 1.1, 1.2, 1.3, etc). If the compose fails quickly from something such as a
failure to have signed packages then it will not be assigned a release candidate.
Per @mohanboddu there is not a durable way to identify the all of the different ways the
special case DOOMed composes occur so they will be assigned an RC number after the
automation is deployed.
The only visible change will be extra gaps in the RC composes in /pub/alt/stage that
represent these extra numbers being inserted to the sequence.
@mohanboddu is fine with this change; does anyone else have objections?
@ausil , @kevin , @puiterwijk please let me know. The initial script PR will be coming
within the next two business days.
To reply, visit the link below or just reply to this email