Sean Whitton wrote: > (B) We don't do anything special, wait for something in the 5.x series > to hit testing in the normal way, and then update the dgit and git > backports. [...] > In any case, since everyone is happy with (B) for at least a week, we > can do (B) for at least a week.
Sorry for the lack of clarity. I think (B) is the right choice, and without any special delays. My previous reply was just about how we would get testing in a good state without blocking Git updates if the dgit 5.x issues Ian mentioned were release-critical, but I don't think that's the situation we're in. > On Fri, Jun 22 2018, Jonathan Nieder wrote: >> Is there somewhere I can read more about that policy? Not that I'm >> complaining :) > > https://backports.debian.org/Contribute/ > > "... you have to ... update your backport when a new version enters > testing ..." Ah, lovely. Thank you. Jonathan
