Dear Developers, It is my great pleasure and honor to officialize the existence and the powers of one of Debian's most important teams: the Release Team. I'd like to stress that the delegation (below, between dashed lines) does _not_ include "get the release in shape by fixing all RC bugs": that stays the collective responsibility of the Project as a whole! Internally, the release team distinguishes between: - Release Managers -- RM: Adam D. Barratt, Niels Thykier; - Stable Release Managers -- SRM: Adam D. Barratt, Philipp Kern; - Release Assistants -- RA: Andreas Barth, Felipe Augusto van de Wiel, Ivo De Decker, Julien Cristau, Jonathan Wiltshire, Cyril Brulebois, Mehdi Dogguy. This distinction is not relevant in terms of delegated powers. - Lucas ---------------------------------------------------------------- Release Team delegation ======================= I hereby appoint the following developers as Release Team members: - Andreas Barth <aba> - Adam D. Barratt <adsb> - Felipe Augusto van de Wiel <faw> - Ivo De Decker <ivodd> - Julien Cristau <jcristau> - Jonathan Wiltshire <jmw> - Cyril Brulebois <kibi> - Mehdi Dogguy <mehdi> - Niels Thykier <nthykier> - Philipp Kern <pkern> The delegation is not time-limited. It will be effective until further changes by present or future DPLs. Task Description ---------------- The Release Team oversees and manages the releases of the testing, stable, and oldstable distributions (aka suites). * Release Team members decide on the release schedule (e.g.; freeze date, release date for stable releases and point-releases for stable and oldstable) * Release Team members define the content of the suites listed above, that is: + They define the packages that are part of those suites. Generally, that is achieved: - by deciding which issues are release-critical (RC) -- making the affected packages not suitable for stable releases -- usually by setting the corresponding bug's severity to serious, grave or critical; - by deciding which package modifications (e.g.; bugfixes) are suitable for inclusion in those suites; - by deciding when and how updated packages migrate between suites. When necessary, they may temporarily forbid specific uploads to unstable in order to facilitate transitions. + They define the ports (architectures) that are part of those suites, by deciding which issues are severe enough to prevent a port from being part of a stable release. * Release Team members decide on the codenames for stable releases. * Release Team members coordinate the work on the release notes, and have the final say on their content. * Release Team members have the final say on the official material for each release (e.g., they decide which CD images are official ones). ----------------------------------------------------------------
Attachment:
signature.asc
Description: Digital signature