From Fedora Project Wiki
(House keeping) |
|||
Line 17: | Line 17: | ||
* [[Fedora_Program_Management/EOLRebaseSOP | End Of Life and Rawhide Rebase]] | * [[Fedora_Program_Management/EOLRebaseSOP | End Of Life and Rawhide Rebase]] | ||
* [[Fedora_Program_Management/ScheduleSOP | Schedule maintenance]] | * [[Fedora_Program_Management/ScheduleSOP | Schedule maintenance]] | ||
= House Keeping = | |||
Previously, house keeping was done in BugZappers wiki but as BugZappers group is dismissed for several years, it was moved to FPgM wiki. | |||
* [[Fedora_Program_Management/HouseKeeping/Fedora22| Fedora 22]] | |||
= Useful links = | = Useful links = |
Revision as of 07:52, 29 May 2015
Fedora Program Manager
Within the Fedora Project, the Program Manager (FPGM) is primarily responsible for:
- planning and scheduling of Fedora releases
- tracking the changes/features during the development/testing cycle
- release coordination (within QA, releng, FESCo, etc.)
- processes behind Fedora Project
- member of Fedora Council - Auxiliary Seat, Council secretary
The position is currently held by Jaroslav Reznik <jreznik@fedoraproject.org> for Fedora 22 and Jan Kurik <jkurik@redhat.com> for Fedora 23+.
Program management SOPs
This SOP (Standard Operating Procedure) section contains a list of common FPGMs tasks.
- The Go/No-Go meeting
- The Readiness meeting
- Change Process
- End Of Life and Rawhide Rebase
- Schedule maintenance
House Keeping
Previously, house keeping was done in BugZappers wiki but as BugZappers group is dismissed for several years, it was moved to FPgM wiki.
Useful links
- Schedules in HTML/ICS formats with TaskJuggler 2 sources
- Fedora Project Schedule Trac to report scheduling issues, and GIT with scripts making FPGM happier
- Fedora Release Life Cycle aka how to schedule next Fedora release