Bug#1127616: developers-reference: should document using git-debpush to upload

* Jochen Sprickerhof: " Re: Bug#1127616: developers-reference: should document
  using git-debpush to upload" (Wed, 11 Feb 2026 13:42:46 +0100):

> * Sean Whitton <[email protected]> [2026-02-11 11:52]:
> >For example, I maintain or team half-maintain maybe 90 packages in
> >total, and none of them use pristine-tar.  So the only case where I
> >cannot use tag2upload is when I need to upload to NEW, which is not
> >often.  Therefore tag2upload is my default way to upload, because why
> >wouldn't it be, it's so smooth and easy.  
> 
> My perception is rather different here:
> 
> Python Team:
> 
> "DPT requires a pristine-tar branch"
> 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> 
> Science Team:
> 
> "It is recommended to use pristine-tar"
> 
> https://science-team.pages.debian.net/policy/
> 
> Multimedia Team:
> 
> "gbp clone --pristine-tar"
> 
> https://wiki.debian.org/DebianMultimedia/DevelopPackaging

May be add:

Tryton Team:

pristine-tar required

Upstream uses mercurial, definitely only approved and supported release path is
via tarballs.