User:Adamwill/Draft releng SOP deliverables

From FedoraProject

< User:Adamwill(Difference between revisions)
Jump to: navigation, search
(add stuff about torrents)
(s/should/must/)
Line 22: Line 22:
 
Once an Alpha release candidate is declared gold, the following must be generated:
 
Once an Alpha release candidate is declared gold, the following must be generated:
  
* A torrent file, compliant with [http://www.bittorrent.org/beps/bep_0003.html BEP-0003], for each of the images described above except the network install images. Each torrent file should be named identically to the image file except that it must have the extension .torrent instead of .iso.
+
* A torrent file, compliant with [http://www.bittorrent.org/beps/bep_0003.html BEP-0003], for each of the images described above except the network install images. Each torrent file must be named identically to the image file except that it must have the extension .torrent instead of .iso.
  
 
=== Beta ===
 
=== Beta ===
Line 43: Line 43:
 
Once a Beta release candidate is declared gold, the following must be generated:
 
Once a Beta release candidate is declared gold, the following must be generated:
  
* A torrent file, compliant with [http://www.bittorrent.org/beps/bep_0003.html BEP-0003], for each of the images described above except the network install images. Each torrent file should be named identically to the image file except that it must have the extension .torrent instead of .iso.
+
* A torrent file, compliant with [http://www.bittorrent.org/beps/bep_0003.html BEP-0003], for each of the images described above except the network install images. Each torrent file must be named identically to the image file except that it must have the extension .torrent instead of .iso.
  
 
=== Final ===
 
=== Final ===
Line 64: Line 64:
 
Once a Final release candidate is declared gold, the following must be generated:
 
Once a Final release candidate is declared gold, the following must be generated:
  
* A torrent file, compliant with [http://www.bittorrent.org/beps/bep_0003.html BEP-0003], for each of the images described above except the network install images. Each torrent file should be named identically to the image file except that it must have the extension .torrent instead of .iso.
+
* A torrent file, compliant with [http://www.bittorrent.org/beps/bep_0003.html BEP-0003], for each of the images described above except the network install images. Each torrent file must be named identically to the image file except that it must have the extension .torrent instead of .iso.
  
 
== Verification ==
 
== Verification ==

Revision as of 02:15, 15 March 2012

Contents

Description

This SOP specifies exactly what builds, signatures, checksums etc release engineering must deliver when building Fedora release composes.

Action

Alpha

Each Alpha test compose should contain the following:

  • A directory tree with two top-level directories named 'Fedora' and 'Live', each of which should contain a sub-directory named after each primary architecture. Within the 'Fedora' top-level directory, each architecture directory should contain two sub-directories, 'iso' and 'os'.
  • A DVD install image, in the ISO 9660 format, for each primary architecture, named according to the formula Fedora-(releasenumber)-Alpha-TC(number)-(arch)-DVD.iso (e.g. Fedora-17-Alpha-TC1-x86_64-DVD.iso). The images ought not to exceed 4,590,208 KiB in size, but this is not strictly mandatory at this point. These images should be located in the /Fedora/(arch)/iso directory.
  • A network install image, in the ISO 9660 format, for each primary architecture, named according to the formula Fedora-(releasenumber)-Alpha-TC(number)-(arch)-netinst.iso (e.g. Fedora-17-Alpha-TC1-x86_64-netinst.iso). The images ought not to exceed 666,000 KiB in size, but this is not strictly mandatory at this point. These images should be located in the /Fedora/(arch)/iso directories.
  • Live booting images, in the ISO 9660 format, for each of the Desktop (GNOME), KDE, XFCE and LXDE spins, for each primary architecture, named according to the formula Fedora-(releasenumber)-Alpha-TC(number)-(arch)-Live-(spinname).iso (e.g. Fedora-17-Alpha-TC1-x86_64-Live-Desktop.iso). The images ought not to exceed 720,000 KiB in size, but this is not strictly mandatory at this point. These images should be located in the /Live/(arch) directory.
  • A single file in each directory in the tree which contains any of the above images, named according to the same formula as the images, but with the final element and the .iso extension replaced by the word CHECKSUM. For example, Fedora-17-Alpha-TC1-x86_64-CHECKSUM and Fedora-17-Alpha-TC1-x86_64-Live-CHECKSUM. This file is to contain a checksum in the sha256sum format for each image file in the same directory, each on a new line, each followed by a space, then an asterisk (*), then the filename of the image. It may contain any number of other lines that begin with a # (denoting comments), and any number of blank lines, but it may not contain anything else.

Each Alpha release candidate must contain the following:

  • A directory tree with two top-level directories named 'Fedora' and 'Live', each of which should contain a sub-directory named after each primary architecture. Within the 'Fedora' top-level directory, each architecture directory must contain two sub-directories, 'iso' and 'os'.
  • A DVD install image, in the ISO 9660 format, for each primary architecture, named according to the formula Fedora-(releasenumber)-Alpha-(arch)-DVD.iso (e.g. Fedora-17-Alpha-x86_64-DVD.iso). The images ought not to exceed 4,590,208 KiB in size, but this is not strictly mandatory at this point. These images must be located in the /Fedora/(arch)/iso directory.
  • A network install image, in the ISO 9660 format, for each primary architecture, named according to the formula Fedora-(releasenumber)-Alpha-(arch)-netinst.iso (e.g. Fedora-17-Alpha-x86_64-netinst.iso). The images ought not to exceed 666,000 KiB in size, but this is not strictly mandatory at this point. These images must be located in the /Fedora/(arch)/iso directories.
  • Live booting images, in the ISO 9660 format, for each of the Desktop (GNOME), KDE, XFCE and LXDE spins, for each primary architecture, named according to the formula Fedora-(releasenumber)-Alpha-(arch)-Live-(spinname).iso (e.g. Fedora-17-Alpha-x86_64-Live-Desktop.iso). The images ought not to exceed 720,000 KiB in size, but this is not strictly mandatory at this point. These images must be located in the /Live/(arch) directory.
  • A single file in each directory in the tree which contains any of the above images, named according to the same formula as the images, but with the final element and the .iso extension replaced by the word CHECKSUM. For example, Fedora-17-Alpha-x86_64-CHECKSUM and Fedora-17-Alpha-x86_64-Live-CHECKSUM. This file is to contain a checksum in the sha256sum format for each image file in the same directory, each on a new line, each followed by a space, then an asterisk (*), then the filename of the image. It may contain any number of other lines that begin with a # (denoting comments), and any number of blank lines, but it may not contain anything else.

Once an Alpha release candidate is declared gold, the following must be generated:

  • A torrent file, compliant with BEP-0003, for each of the images described above except the network install images. Each torrent file must be named identically to the image file except that it must have the extension .torrent instead of .iso.

Beta

Each Beta test compose should contain the following:

  • A directory tree with two top-level directories named 'Fedora' and 'Live', each of which should contain a sub-directory named after each primary architecture. Within the 'Fedora' top-level directory, each architecture directory should contain two sub-directories, 'iso' and 'os'.
  • A DVD install image, in the ISO 9660 format, for each primary architecture, named according to the formula Fedora-(releasenumber)-Beta-TC(number)-(arch)-DVD.iso (e.g. Fedora-17-Beta-TC1-x86_64-DVD.iso). The images should not exceed 4,590,208 KiB in size. These images should be located in the /Fedora/(arch)/iso directory.
  • A network install image, in the ISO 9660 format, for each primary architecture, named according to the formula Fedora-(releasenumber)-Beta-TC(number)-(arch)-netinst.iso (e.g. Fedora-17-Beta-TC1-x86_64-netinst.iso). The images should not exceed 666,000 KiB in size. These images should be located in the /Fedora/(arch)/iso directories.
  • Live booting images, in the ISO 9660 format, for each of the Desktop (GNOME), KDE, XFCE, LXDE and SoaS (Sugar) spins, for each primary architecture, named according to the formula Fedora-(releasenumber)-Beta-TC(number)-(arch)-Live-(spinname).iso (e.g. Fedora-17-Beta-TC1-x86_64-Live-Desktop.iso). The images should not exceed 720,000 KiB in size. These images should be located in the /Live/(arch) directory.
  • A single file in each directory in the tree which contains any of the above images, named according to the same formula as the images, but with the final element and the .iso extension replaced by the word CHECKSUM. For example, Fedora-17-Beta-TC1-x86_64-CHECKSUM and Fedora-17-Beta-TC1-x86_64-Live-CHECKSUM. This file is to contain a checksum in the sha256sum format for each image file in the same directory, each on a new line, each followed by a space, then an asterisk (*), then the filename of the image. It may contain any number of other lines that begin with a # (denoting comments), and any number of blank lines, but it may not contain anything else.

Each Beta release candidate must contain the following:

  • A directory tree with two top-level directories named 'Fedora' and 'Live', each of which should contain a sub-directory named after each primary architecture. Within the 'Fedora' top-level directory, each architecture directory must contain two sub-directories, 'iso' and 'os'.
  • A DVD install image, in the ISO 9660 format, for each primary architecture, named according to the formula Fedora-(releasenumber)-Beta-(arch)-DVD.iso (e.g. Fedora-17-Beta-x86_64-DVD.iso). The images must not exceed 4,590,208 KiB in size. These images must be located in the /Fedora/(arch)/iso directory.
  • A network install image, in the ISO 9660 format, for each primary architecture, named according to the formula Fedora-(releasenumber)-Beta-(arch)-netinst.iso (e.g. Fedora-17-Beta-x86_64-netinst.iso). The images must not exceed 666,000 KiB in size. These images must be located in the /Fedora/(arch)/iso directories.
  • Live booting images, in the ISO 9660 format, for each of the Desktop (GNOME), KDE, XFCE, LXDE and SoaS (Sugar) spins, for each primary architecture, named according to the formula Fedora-(releasenumber)-Beta-(arch)-Live-(spinname).iso (e.g. Fedora-17-Beta-x86_64-Live-Desktop.iso). The images must not exceed 720,000 KiB in size. These images must be located in the /Live/(arch) directory.
  • A single file in each directory in the tree which contains any of the above images, named according to the same formula as the images, but with the final element and the .iso extension replaced by the word CHECKSUM. For example, Fedora-17-Beta-x86_64-CHECKSUM and Fedora-17-Beta-x86_64-Live-CHECKSUM. This file is to contain a checksum in the sha256sum format for each image file in the same directory, each on a new line, each followed by a space, then an asterisk (*), then the filename of the image. It may contain any number of other lines that begin with a # (denoting comments), and any number of blank lines, but it may not contain anything else.

Once a Beta release candidate is declared gold, the following must be generated:

  • A torrent file, compliant with BEP-0003, for each of the images described above except the network install images. Each torrent file must be named identically to the image file except that it must have the extension .torrent instead of .iso.

Final

Each Final test compose should contain the following:

  • A directory tree with two top-level directories named 'Fedora' and 'Live', each of which should contain a sub-directory named after each primary architecture. Within the 'Fedora' top-level directory, each architecture directory should contain two sub-directories, 'iso' and 'os'.
  • A DVD install image, in the ISO 9660 format, for each primary architecture, named according to the formula Fedora-(releasenumber)-TC(number)-(arch)-DVD.iso (e.g. Fedora-17-TC1-x86_64-DVD.iso). The images should not exceed 4,590,208 KiB in size. These images should be located in the /Fedora/(arch)/iso directory.
  • A network install image, in the ISO 9660 format, for each primary architecture, named according to the formula Fedora-(releasenumber)-TC(number)-(arch)-netinst.iso (e.g. Fedora-17-TC1-x86_64-netinst.iso). The images should not exceed 666,000 KiB in size. These images should be located in the /Fedora/(arch)/iso directories.
  • Live booting images, in the ISO 9660 format, for each approved spin, for each primary architecture, named according to the formula Fedora-(releasenumber)-TC(number)-(arch)-Live-(spinname).iso (e.g. Fedora-17-TC1-x86_64-Live-Desktop.iso). The images should not exceed the size targeted by the group responsible for the spin. These images should be located in the /Live/(arch) directory.
  • A single file in each directory in the tree which contains any of the above images, named according to the same formula as the images, but with the final element and the .iso extension replaced by the word CHECKSUM. For example, Fedora-17-TC1-x86_64-CHECKSUM and Fedora-17-TC1-x86_64-Live-CHECKSUM. This file is to contain a checksum in the sha256sum format for each image file in the same directory, each on a new line, each followed by a space, then an asterisk (*), then the filename of the image. It may contain any number of other lines that begin with a # (denoting comments), and any number of blank lines, but it may not contain anything else.

Each Final release candidate must contain the following:

  • A directory tree with two top-level directories named 'Fedora' and 'Live', each of which should contain a sub-directory named after each primary architecture. Within the 'Fedora' top-level directory, each architecture directory must contain two sub-directories, 'iso' and 'os'.
  • A DVD install image, in the ISO 9660 format, for each primary architecture, named according to the formula Fedora-(releasenumber)-(arch)-DVD.iso (e.g. Fedora-17-x86_64-DVD.iso). The images must not exceed 4,590,208 KiB in size. These images must be located in the /Fedora/(arch)/iso directory.
  • A network install image, in the ISO 9660 format, for each primary architecture, named according to the formula Fedora-(releasenumber)-(arch)-netinst.iso (e.g. Fedora-17-x86_64-netinst.iso). The images must not exceed 666,000 KiB in size. These images must be located in the /Fedora/(arch)/iso directories.
  • Live booting images, in the ISO 9660 format, for each approved spin, for each primary architecture, named according to the formula Fedora-(releasenumber)-(arch)-Live-(spinname).iso (e.g. Fedora-17-x86_64-Live-Desktop.iso). The images must not exceed the size targeted by the group responsible for the spin. These images must be located in the /Live/(arch) directory.
  • A single file in each directory in the tree which contains any of the above images, named according to the same formula as the images, but with the final element and the .iso extension replaced by the word CHECKSUM. For example, Fedora-17-x86_64-CHECKSUM and Fedora-17-x86_64-Live-CHECKSUM. This file is to contain a checksum in the sha256sum format for each image file in the same directory, each on a new line, each followed by a space, then an asterisk (*), then the filename of the image. It may contain any number of other lines that begin with a # (denoting comments), and any number of blank lines, but it may not contain anything else.

Once a Final release candidate is declared gold, the following must be generated:

  • A torrent file, compliant with BEP-0003, for each of the images described above except the network install images. Each torrent file must be named identically to the image file except that it must have the extension .torrent instead of .iso.

Verification

Verification can be achieved by manually examining the tree generated by the image creation process and ensuring it meets the requirements.