Updating the Release Team delegation

[Chris Lamb <lamby@debian.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear Developers,

I hereby appoint the following as members of the Debian Release Team:

 * Managers:
   - Emilio Pozuelo Monfort (pochu)
   - Niels Thykier (nthykier)

 * Stable Release Managers (SRM):
   - Adam D. Barratt (adsb)
   - Julien Cristau (jcristau)
   - Philipp Kern (pkern)

 * Release Assistants:
   - Andreas Barth (aba)
   - Cyril Brulebois (kibi)
   - Felipe Augusto van de Wiel (faw)
   - Ivo De Decker (ivodd)
   - Jonathan Wiltshire (jmw)
   - Mehdi Dogguy (mehdi)
   - Paul Gevers (elbrus)

This represents the addition of Paul Gevers (elbrus) who will be
joining as a Release Assistant.

Any previous Release Team delegation not explicitly listed above is
revoked. The delegation is not time-limited; it will be effective
until further changes by present or future Project Leaders.


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
   dates, release dates for stable 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) (ie. making the affected
       packages not suitable for stable releases) usually by setting
       the corresponding bug's severity to serious, grave or critical.

     - Which package modifications (eg. bug fixes) are suitable for
       inclusion in those suites.

     - 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 architectures (ports) that are part of those
     suites by deciding which issues are severe enough to prevent a
     given 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 such as deciding which CD images are "official"
   ones.


Appendix
- --------

You can learn more about the activities and responsibilities of the
Release Team here:

  https://wiki.debian.org/Teams/ReleaseTeam


Regards,

- -- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org 🍥 chris-lamb.co.uk
       `-

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlxPPtQACgkQHpU+J9Qx
Hljsug/8DSSO7QoGrXve70pfmMTsjJXTQAajEkc69Ed6J3OAcN5C2hDJmwGHJjWI
beiqpBhAAzeY4n8mVWSX+k7Y5oqZb2R/7Px6kIx+uW17mS3QMeSiQYSX7WLa8Pox
aedwDGBEsFqm6u/QE2Az5Gq6Vz9jMk7tfQJoY4TEtgqUEwUUBcG1kuyrQoaFyvUv
HA8pP6OPh9RN7Xb4mn01o9OJudU5+3vC/NsyMeeZixx/sCExOuY/gJK/adRVYbq9
ncvvmGMVcflyiNVOdIt27RGbCsMRYjwVlIwULmuI3jYnYxE4f/ewGVfTaEU+p9rY
PImGm4lqhOzQONSjAEutarqYPnmPQHlmmDr4lFq3AATXV2+hdcSwHiEH7bQySGGw
mtrWwxOD/6CpsgtgFDHq+c6cOE3I2vW3sSmYO0JZ0iO5xgFgFarK9LZHf4lGwF6T
r3eIN9bsbAVax9MGfG6zq0aagQLypQBeq1ZT9SAo0QVBvyzsqcFoKJm03iJcFzFH
XWTiAwBbznGNIKpuMOkpnycC0OKlnO8A2fhyd0CXbHTPy+CzyYvCTXm7XJ+HIrKu
qygPu07MW59ui3uR733aEaVElpJDIWHsk9oMPfd3LTMKOVMu4RTMeQGKon5J08Rt
8fdDuhkO/LshYTohoZnoGvHnF7Ep+QI8RXMCvUcJ3CSB4OhJti4=
=dspT
-----END PGP SIGNATURE-----