Hi Sean, Sean Whitton wrote: > On Fri, Jun 22 2018, Jonathan Nieder wrote:
>> Do you plan to update dgit in backports once it hits testing? > > Yes. Excellent, thank you. [...] >> Is there anything I can do to help? For example, should I prepare an >> upload for 4.4 while we wait for 5.1 to migrate to testing? > > So far as I can tell from this bug's metadata 4.4 will not help you? > (I'll push 4.4 to stretch-backports soon in order to comply with > backports policy, anyway.) Is there somewhere I can read more about that policy? Not that I'm complaining :). [...] > On Fri, Jun 22 2018, Ian Jackson wrote: >> However, we have just released a major new feature and there are >> inevitble bugs in it. My current wip branch[1] has fixes for that but >> also fixes for other bugs, some of which may themselves cause further >> bugs. [...] > The only way to delay > updating the backport is to keep making releases to unstable ;) Or in other words, users of the backport are not promised any better stabilization than testing. If you're concerned about the stability of the package, I recommend sorting it out in testing too, as mentioned in my previous reply. Thanks much, Jonathan
