[Resending whole thing. I think it is is important to have it publicly available and to reach you, so adding it to the bugreport too. Apparently team+dns@tracker.d.o isn't working and there's no archives]
I want to follow up on the todays ldns incident. I think it was quite interesting. The whole thing of me pushing the 1.7.1-2.1 NMU was not noticed by the current maintainer of ldns package. I don't know why, but after uploading to DELAYED/2, I thought I'd ask Santiago directly, because strangely I did see his reply to other emails but not to my upload. And indeed, he replied he didn't receive my nmudiff emails about the delayed upload. So next, instead of me ensuring the comminication is working correctly, I switched to mostly private email exchange between me and Santiago. We discussed many things, he reviewed my changes, we discussed possible master branch rewrite (the top two commits by Robert), I've asked Robert about his opinion on these 2 commits, -- this all has been done in private email exchange. I was wrong here not to add some Cc to team+dns@ or some bugreport, or anything. On the contrary, the discussion spinned off the python3.10 ftbfs bug, but I replied to Santiago in private, because that discussion has nothing to do with that bugreport really. So initially it was me who made whole thing absolutely unknown to all the dns team, whole team was absolutely unaware about the happenings in there. I apologize for this discussion going on entirely in private. The problem was not because of my incompetence or me being unaware, no, *that*'d be understandable. The thing was that I had this thought many times, I had this feeling every time I replied, that this whole thing should be made public, but I didn't do anything with that, -- the usual "I don't have time right now for this" played its game. And sure thing, Daniel did the best he thought it is, without any knowledge about all the happenings behind the scenes. Hopefully the whole thing is much better now. Yes it required master branch rewrite, because of *my* NMU which went out of order. And it was still the same single rewrite after Daniel changes. Now, to sum it up: mjt-1.8 branch *was* ready for the upload (tho I was more comfortable with another 1.7 upload too). Now I need to review it before it can be merged (now it's just fast-forward, but please let me one more chance for mjt-1.8 branch rewrite if I'll find anything in there which needs a rebase - I'm not asking about master branch rewrite here). I kept it separate from master for 2 reasons now: first I need to review it myself, and second, if by a chance we'll have to fix the 1.7.1-3 upload, we wont need another rewrite. [While I experimented with team+dns@tracker.d.o, I also force-pushed mjt-1.8 branch again, fixing changelog so it will not include already listed entries, and adding two more commits to there. I'm still not entirely sure what I have in there is what I actually want it to be, so I still have to re-review my own changes - whenever they're making sense on top of Daniel's changes. Please be patient there] Thank you all for the patience. This was a good lesson for everyone, I think. /mjt
