On Thu, Nov 24, 2016, at 13:39, Philipp Kern wrote: > So if you, as an upstream maintainer, have a change that is needed for > compatibility with changes in network APIs and the change is reviewable > by humans, a stable update could be possible. It's still on a > case-by-case basis, so you would need to ask and the Release Team cannot > approve what they do not know about.
There are more cases where Debian stable is getting new upstream releases. It's mostly to keep up with the security (MySQL, PHP), but I guess that approaching debian-release team and pre-negotiating with them would be helpful. Peter, there's one more question embedded within what you have already asked: - would new versions of python-certbot and python-acme require new python libraries? If yes (or maybe), then the answer would be: go with stretch-backports. But if you can use whatever will be in next Debian stable, it might be feasible to negotiate with Debian release team to push the new upstream releases via s-p-u. (However I am not speaking for or on behalf of the release team.) Cheers, -- Ondřej Surý <ond...@sury.org> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware, fast DNS(SEC) resolver Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro pečení chleba všeho druhu