Ensure it builds on all architectures in testing, where it built previously.

Check the auto-generated "auto-<source>" ben tracker. If not useful (or if it does not appear) generate an applicable one and include it in your request for a transition slot (see below).

Test rebuild reverse dependencies

Request a transition slot from the release team (reportbug release.debian.org)

Wait for ACK

Upload to unstable after ACK

NMU reverse dependencies as needed.

The Request

Please request a transition slot from the Release Team by filing a transition bug report against release.debian.org (reportbug has a template). In some cases (major transitions), it might be prudent to also send an email to debian-devel-announce, but please see the section below on that subject.

In the transition bug report, please include the list of affected source packages and what needs to be done with each of them. In some cases, a lot of binNMUs will be enough (e.g. a clean library ABI bump) though in other cases sourceful uploads are required (e.g. API change).

Please do not upload the package to unstable without approval from the release team.

debian-devel-announce mails

If you are sending an email to d-d-a about the transition, here are some recommendations.

Reference the transition bug report. People tend to ask if you do not.

Avoid using specific upload dates, unless they have been approved by the Release Team.

We do not like NACK'ing a d-d-a mail on d-d-a. It just is not pretty, but it is far better than entangled transitions.

Speeding up transitions

Here are some hints to getting your transitions started and finished sooner.

Upload to experimental.

This will ensure your new package has cleared the NEW queue and we can promptly start the transition.

For the general case, it will also create an "auto-<source>" ben tracker.