| 25 | | |
| 26 | | == The FDO Release Manager Role == |
| 27 | | |
| 28 | | For every release of FDO, the PSC elects a release manager (this is usually done with a motion and vote on the fdo-internals list). |
| 29 | | |
| 30 | | The overall role of the release manager is to coordinate the efforts of the developers, testers, documentation and other contributors to lead to a release of the best possible quality within the scheduled timeframe. |
| 31 | | |
| 32 | | The PSC delegates to the release manager the responsibility and authority to make certain final decisions for a release, including:[[BR]] |
| 33 | | |
| 34 | | * Approving or not the release of each beta, release candidate and final release [[BR]] |
| 35 | | * Approving or rejecting non-trivial bug fixes or changes after the feature freeze [[BR]] |
| 36 | | * Maintaining the release schedule (timeline) and making changes as required [[BR]] |
| 37 | | * When in doubt or for tough decisions (e.g. pushing the release date by several weeks) the release manager is free to ask the PSC to vote in support of some decisions, but this is not a requirement for the areas of responsibility above.[[BR]] |
| 38 | | |
| 39 | | The release manager's role also includes the following tasks:[[BR]] |
| 40 | | |
| 41 | | * Setup and maintain the Release Plan section of the website for this release [[BR]] |
| 42 | | * Coordinate with the developers team [[BR]] |
| 43 | | * Coordinate with the QA/testers team [[BR]] |
| 44 | | * Coordinate with the docs/website team [[BR]] |
| 45 | | * Keep track of progress via Trac (make use of Trac milestones and ensure tickets are properly targeted, push some tickets to a later release if required, etc.) [[BR]] |
| 46 | | * Organize regular IRC meetings (including agenda and minutes) [[BR]] |
| 47 | | * Tag source code in SVN for each beta, RC and release [[BR]] |
| 48 | | * Branch source code in SVN after the final release (trunk becomes the next dev version) [[BR]] |
| 49 | | * Package source code distribution for each beta/RC/release [[BR]] |
| 50 | | * Update appropriate website/download page for each beta/RC/release [[BR]] |
| 51 | | * Make announcements on fdo-users and fdo-announce for each release [[BR]] |
| 52 | | * Produce/coordinate bugfix releases as needed during the 6 months period that follows the final release (i.e. until the next release) [[BR]] |
| 53 | | * Any of the above tasks can be delegated but they still remain the ultimate responsibility of the release manager.[[BR]] |
| 54 | | |
| | 77 | For every release of FDO, the PSC elects a release manager (this is usually done with a motion and vote on the fdo-internals list). |
| | 78 | |
| | 79 | The overall role of the release manager is to coordinate the efforts of the developers, testers, documentation and other contributors to lead to a release of the best possible quality within the scheduled timeframe. |
| | 80 | |
| | 81 | The PSC delegates to the release manager the responsibility and authority to make certain final decisions for a release, including:[[BR]] |
| | 82 | |
| | 83 | * Approving or not the release of each beta, release candidate and final release [[BR]] |
| | 84 | * Approving or rejecting non-trivial bug fixes or changes after the feature freeze [[BR]] |
| | 85 | * Maintaining the release schedule (timeline) and making changes as required [[BR]] |
| | 86 | * When in doubt or for tough decisions (e.g. pushing the release date by several weeks) the release manager is free to ask the PSC to vote in support of some decisions, but this is not a requirement for the areas of responsibility above.[[BR]] |
| | 87 | |
| | 88 | The release manager's role also includes the following tasks:[[BR]] |
| | 89 | |
| | 90 | * Setup and maintain the Release Plan section of the website for this release [[BR]] |
| | 91 | * Coordinate with the developers team [[BR]] |
| | 92 | * Coordinate with the QA/testers team [[BR]] |
| | 93 | * Coordinate with the docs/website team [[BR]] |
| | 94 | * Keep track of progress via Trac (make use of Trac milestones and ensure tickets are properly targeted, push some tickets to a later release if required, etc.) [[BR]] |
| | 95 | * Organize regular IRC meetings (including agenda and minutes) [[BR]] |
| | 96 | * Tag source code in SVN for each beta, RC and release [[BR]] |
| | 97 | * Branch source code in SVN after the final release (trunk becomes the next dev version) [[BR]] |
| | 98 | * Package source code distribution for each beta/RC/release [[BR]] |
| | 99 | * Update appropriate website/download page for each beta/RC/release [[BR]] |
| | 100 | * Make announcements on fdo-users and fdo-announce for each release [[BR]] |
| | 101 | * Produce/coordinate bugfix releases as needed during the 6 months period that follows the final release (i.e. until the next release) [[BR]] |
| | 102 | * Any of the above tasks can be delegated but they still remain the ultimate responsibility of the release manager.[[BR]] |
| | 103 | |
| | 104 | |
