[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Updating the Release Team delegation

Dear Developers,

It is my pleasure to announce that Emilio Pozuelo Monfort (pochu) is
joining the Release Team as a Release Assistant. The updated delegation
is provided below (between dashed lines). The tasks description is

It is worth noting that this addition is an indirect outcome of the
GNOME sprint[1]: discussions about how the experience of transitions
could be improved took place, and Emilio offered to join the Release
Team and help process transitions, both those related to GNOME packages
and others, as well as helping with other day-to-day release tasks.
The Release Team welcomed the idea.

[1] https://wiki.debian.org/Sprints/2014/SystemdGNOMESprint

Welcome, Emilio!

- 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>
- Emilio Pozuelo Monfort <pochu>

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

 * 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
     - 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


Attachment: signature.asc
Description: Digital signature

Reply to: