(Add content from old page) |
Maxamillion (talk | contribs) No edit summary |
||
| 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]}} | |||
This page documents the Standard Operating Procedures for Fedora Release Engineering. | This page documents the Standard Operating Procedures for Fedora Release Engineering. | ||
Latest revision as of 17:48, 3 November 2015
All Fedora Release Engineering Documentation has moved here with source hosted along side the code in the releng pagure repository
This page documents the Standard Operating Procedures for Fedora Release Engineering.
Purpose
The SOP section contains a list of tasks Fedora Release Engineering team provides for the project. Current Fedora Release Engineering team members would can add tasks they know about and list steps to complete the task as well as issues to consider. This is a great way to make sure that individuals aren't the only ones that can fix a problem.
The Community
The SOP section of the wiki is left in the public because it is our hope that others in the community will add common problems, fix our steps and just in general look over what we're doing and help us when we're doing something stupid. This is a wiki and in true wiki fashion we encourage anyone interested to go over our processes with a fine tooth comb. It'll make us better and we'll probably learn something in the process. General rule, make change first, ask questions later. Many people are watching the wiki so if something is not right, we'll fix it or revert the page.
Procedures
Needed:
- Composing an official release
- Making a composed release publicly available
Pages in category "Release Engineering SOPs"
The following 33 pages are in this category, out of 33 total.