(Link to Mass Branching SOP) |
m (Add Category) |
||
| Line 24: | Line 24: | ||
1. Composing an official release | 1. Composing an official release | ||
1. Making a composed release publicly available | 1. Making a composed release publicly available | ||
[[Category:Release Engineering SOP]] | |||
Revision as of 18:07, 14 February 2009
Fedora Release Engineering Standard Operating Procedures
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:
1. Composing an official release
1. Making a composed release publicly available