#4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent
files, signatures, checksums etc should be provided with (pre)-releases
-----------------------+-----------------------
Reporter: adamwill | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: other
Resolution: | Keywords:
Blocked By: | Blocking:
-----------------------+-----------------------
Comment (by ralph):
On PDC, two things:
- PDC stores the list of things that we actually did produce (by way of
importing the metadata output from pungi).
- When we first started looking at it, we were thinking about also storing
the list of things we *should* produce in a compose as well (which would
meet the criteria for this ticket). While the PDC authors were originally
receptive to that idea, it seems there is concern out there that the scope
of PDC is growing too large and so pushing for an expansion to handle this
case may meet with opposition from upstream.
Another idea: since we keep our pungi config public here
https://pagure.io/pungi-fedora/raw/master/f/fedora.conf and since it
actually defines what we will try to produce, we could build separate
tooling around it that reads it in and parses it to produce a list of
expected outputs. (And we could go back in the git history to figure out
what we intended to produce at some date in the past.)
--
Ticket URL: <
https://fedorahosted.org/rel-eng/ticket/4986#comment:14>
Fedora Release Engineering <
http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project