[Pkg-privacy-maintainers] New upstream release of MAT

[Sascha Steinbiss]

Hi intrigeri,

thanks for the detailed and very informative reply!

>> Is it OK for anyone to just
>> push such updates to Alioth and ping the mailing list for sponsoring afterwards?
> 
> As far as I'm concerned, it's totally fine this way. Please go ahead!

OK. What’s your preferred way of handling such situations — should I add myself to Uploaders: in d/control or mark my new versions as team uploads?

>> I made sure to
>> also fetch the changes in upstream’s git history and used gbp-import-orig’s
>> '--upstream-vcs-tag’ option to link to their release tag, as advised earlier
>> by intrigeri.
> 
> I'm very thankful that you did it, I find it very useful in particular
> due to the strong links between the MAT upstream project, the Tails
> project, and Debian's pkg-privacy.

OK, good to hear that.

> Let me provide a bit more context wrt. the MAT project, and the role
> I've been playing so far: upstream has no peer-review process in place
> as it is essentially a one-man project; for various reasons, and
> perhaps due to mixing up too many hats, for years I've kinda been the
> 3rd and 4th eyes that look at the upstream code changes before they
> land into Debian.

I see. This indeed explains why there is some intermingling of upstream and packaging work done by you, which I noticed (and may have been one of the reasons why I asked in the first place).

> I felt it had to
> be clearly told, but I'm not very concerned about it: I'll simply do
> such code reviews either after the fact on the Debian side (unless I'm
> told it has been done already, of course!).

I would be very happy if you could continue doing that. Your expertise is invaluable and the last thing I would want to do is impact code quality by disturbing a working system ;)

Thanks,
Sascha