Fedora Release Engineering Standard Operating Procedures
This page documents the Standard Operating Procedures for Fedora Release Engineering.
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 SOP section 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. 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. Therefore please open a pull request to suggest improvements.
Standard Operating Procedures
sop_adding_build_targets sop_adding_content_generator sop_adding_new_release_engineer sop_adding_new_branch_sla sop_adding_packages_compose_artifact sop_adding_side_build_targets sop_branch_freeze sop_branching sop_breaking_development_freeze sop_composing_fedora sop_clean_amis sop_create_release_signing_key sop_deprecate_ftbfs_packages sop_end_of_life sop_eol_change sop_mass_branching sop_bodhi_activation sop_mass_rebuild_packages sop_mass_rebuild_modules sop_file_ftbfs sop_generating_openh264_composes sop_package_blocking sop_package_unblocking sop_process_dist_git_requests sop_promoting_container_content sop_signing_builds sop_pushing_updates sop_release_package_signing sop_remote_dist_git_branches sop_requesting_task_automation_users sop_retire_orphaned_packages sop_sigul_client_setup sop_stage_final_release_for_mirrors sop_unretire sop_update_critpath sop_update_releng_docs sop_updating_comps sop_fedora_media_writer sop_find_module_info sop_release_container_base_image
Want to help? Learn how to contribute to Fedora Docs ›