Bits: new policy on out-of-sync and Release Team composition
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear all,
More announcements will follow soon, but here are some bits from the
Release Team.
out-of-sync unstable-to-testing is now RC
=========================================
- From now on the Release Team will consider packages that are
out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug.
If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot
be fixed via unstable. Additionally, blocked packages can have impact
on other packages, which makes preparing for the release more
difficult. Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.
For now, this will be handled via severity:serious bugs in the BTS.
This means the maintainers can interact with the bug reports as with
other RC issues.
These bugs will trigger auto-removal where appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.
If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.
Changes to the Release Team
===========================
It is with great please that we announce our new team member Graham
Inggs <ginggs>. Graham has been working as a non-delegated trainee for
the last couple of months. We have asked our DPL to formally delegate
Graham to the team, which we expect to happen shortly.
At the same time, the team acknowledges the resignation of Andreas
Barth <aba>, Felipe Augusto van de Wiel <faw>, Mehdi Dogguy <mehdi>,
Niels Thykier <nthykier> and Philipp Kern <pkern> from the team. The
remaining team members would like to thank all of them very much for
their contributions to the team over the years.
On behalf of the release team
Paul <elbrus>
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl5H0NYACgkQnFyZ6wW9
dQrgqQf8DGhK4faK4Cu4cyycQo+EYcsTamTDsHDObxCM4l612XoZYBNbg1aytzhc
S4kFedGpxGsjRV0DipXSXnprp6NrTYYsF4LeeShqwoDhsqj027X2PW2IASRcr2IL
1+1k/CCcMdxpc1QQqqbj5W6pElPzRIkuLLMiDZc2ib4JfS3btmOcGHpOsCXQxU27
iqraqke4BjjO18f0q5fdQ0+vfGrMBI5tePHUaE9d9wsNHoWbtPjAplAumzLjw33m
azXnyBfjVUfzNOMIlx8+3PZIbIclVCn0xGdLhbi0ioEmpc+DvEL67uib7kwDL58g
4D7b6M6RJLBp1MsGq+dnH3uGoxdQDA==
=SjBC
-----END PGP SIGNATURE-----
Reply to: