On 12/06/2017 11:49, Drew Parsons wrote:
I wonder whether this should be listed in Debian Science policy as a
general policy?: new major updates (especially transitions with a
soname change) should always be pushed first to experimental.
Otherwise you risk the danger where one component of the library gets
into unstable and then testing, while another component is held back by
some failure. That might result in the library not working at all, for
a while.
Experimental also gives the opportunity to test the builds (and
runtime) of client programs before releasing to unstable.
It is also what Release Team would like you to do, before filing a bug
requesting a transition slot:
https://wiki.debian.org/Teams/ReleaseTeam/Transitions
