proposed-migration, "SMOOTH_UPDATES", and NBS reports

[Sebastien Bacher]

Hey Steve,

Thanks for the email explaining the change, I've some questions

Le 07/12/2021 à 07:56, Steve Langasek a écrit :
> The flipside is that this now means more packages will make it to the
> release pocket while there are still reverse-dependencies of an old library
> name; so when folks are working on proposed-migration, such as for +1
> Maintenance, more attention will need to be paid to cleaning up these
> stragglers.

  So you started by stating the change has been made to help on the 
openssl3 transition, it's a bit unclear to me if you mean it as a 
temporary thing or if you are suggesting that configuration to stay the 
default going forward?

  If the option is the proposed new default, what's the position of the 
release team on having NBS binaries around for the release? I guess that 
in principle we would want to clean that report, but in practice if we 
don't enforce that at proposed migration and lower the pressure to get 
those things resolved it's likely that we end building up debts we don't 
manage to pay.

Cheers,
Sebastien Bacher