> But forcing every maintainer that probably had an agenda for their
> package already, to comply to yours without even knowing what's coming
> is at the very least tactless and disruptive.
the new dpkg was in experimental for a long enough time, and this was
announced often enough. If packages run into trouble with it now, it's
imho not the problem of the dpkg maintainer (except there're bugs in
dpkg, of course).