From Fedora Project Wiki
m (moved ReleaseEngineering/SOP/CustomSpins to Release Engineering - Custom Spins SOP: searchable) |
Maxamillion (talk | contribs) No edit summary |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source hosted along side the code in the [https://pagure.io/releng releng pagure repository]}} | |||
{{admon/important | Incomplete SOP| This Standard Operating Procedure (SOP) is still under construction}} | |||
== Description == | == Description == | ||
Release Engineering is responsible for producing the final .ISO and torrent files for custom spins that are approved by the Fedora Board | Release Engineering is responsible for producing the final .ISO and torrent files for custom spins that are approved by the Fedora Board. This page should explain how to perform both of those tasks. | ||
== Action == | == Action == | ||
Line 10: | Line 14: | ||
--> | --> | ||
== | == Consider Before Running == | ||
<!-- Create a list of things to keep in mind when performing action. | <!-- Create a list of things to keep in mind when performing action. | ||
--> | --> | ||
Line 16: | Line 20: | ||
<!-- Be sure to remove the Category listed below. | <!-- Be sure to remove the Category listed below. | ||
--> | --> | ||
[[Category:Release Engineering SOPs]] | [[Category:Release Engineering SOPs]] | ||
Latest revision as of 17:52, 3 November 2015
Description
Release Engineering is responsible for producing the final .ISO and torrent files for custom spins that are approved by the Fedora Board. This page should explain how to perform both of those tasks.