Ticket #4986 (new task)

Opened 2 years ago

Last modified 9 months ago

Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases

Reported by: adamwill Owned by: rel-eng@…
Milestone: Component: other
Keywords: Cc: ausil, robatino, nirik, jdulaney
Blocked By: Blocking:

Description

Going through the F16 QA retrospective, there's this series of linked points from Andre Robatino:

"robatino - Alpha and Beta torrents often have unsigned checksum files - this just happened with 16 Alpha. It also happened during F13 and F14 - see http://lists.fedoraproject.org/pipermail/test/2010-April/090106.html for F13 Beta, and https://bugzilla.redhat.com/show_activity.cgi?id=638738 for F14 Alpha and Beta. When it's pointed out, we're told that it's not feasible to change them once people have started downloading, but if this is true, there needs to be better checking (at least as much as for mirror content, which can be changed) to make sure the torrents are correct before being posted. Filed https://fedorahosted.org/fedora-qa/ticket/237 and https://fedorahosted.org/rel-eng/ticket/4906 . No response from releng as of yet. Unless QA is given access prior to public posting, it is powerless to prevent this. robatino - Also, it's possible that the checksum files can be signed more than once. There are two versions of the signed checksum files for F15, one on the torrents (the original ones) and a different one on the mirrors. See http://robatino.fedorapeople.org/checksums/15-Final/ for the two versions - for example, Fedora-15-i386-CHECKSUM.orig and Fedora-15-i386-CHECKSUM. While not nearly as serious as the above issue (since the checksums are the same and both signatures are good), it could be confusing. "

A quick mail discussion prompted the suggestion from Andre that the best way to cover all these issues would be for there to be a Deliverables wiki page / SOP which clearly lists all the 'bits' that should be delivered for each image drop - Alpha, Beta, Final, TC and RC. This would provide a simple reference for whoever's doing the build to make sure everything has been provided.

It would make most sense for this to live in releng's wiki space, I think, so filing against releng trac, but a QA person could certainly take care of creating the page in theory, I think.

We should have this in place prior to F17 Alpha TC1.

Change History

comment:1 Changed 2 years ago by adamwill

  • Cc dennis@…, robatino, nirik added

Apologies - the suggestion was from Kevin Fenzi, not Andre.

comment:2 Changed 2 years ago by ausil

  • Cc ausil added; dennis@… removed

comment:3 Changed 2 years ago by jdulaney

  • Cc jdulaeny added

comment:4 Changed 2 years ago by jdulaney

  • Cc jdulaney added; jdulaeny removed

comment:5 Changed 9 months ago by till

  • Component changed from koji to other

this does not seem to be a koji-related ticket

Note: See TracTickets for help on using tickets.