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

Hello,

Otto Kekäläinen [10/Feb 11:54pm +08] wrote:
> The tag2upload service is tightly coupled with dgit, and while dgit by
> design will never support pristine-tar type of ability to reproduce
> upstream tarballs bit-for-bit, it should at least have the actual
> upstream signed tags instead (from upstreams that publish them).

This is completely false.

There are no fundamental design blockers for any of this.

> There were already suggestions on debian-devel@ that maintainers
> should use dgit push for the initial -1 upload and git debpush for the
> -1+N uploads. That is obviously overly complex and shows that this is
> not ready to be recommended to newbies in the developers reference.

This advanced workflow might be useful to some maintainers and I'm glad
to see them discussing it, but it's not what the tag2upload Delegates
would recommend to newcomers -- we do not need to do that.

-- 
Sean Whitton

-----BEGIN PGP SIGNATURE-----

iQJNBAEBCgA3FiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmmLav0ZHHNwd2hpdHRv
bkBzcHdoaXR0b24ubmFtZQAKCRBpW3rkvwZiQDEgD/9cXnT5Sd5GY4Hl2xjpTFUO
X2RGCPy1vmIPAIWok5BdO4hFuFlX1gkT582t113Vwygl4CpqvvgwXFQAseTUYAOz
Q6Mg2cFGdN9sY/vQcS+kOpWNuwndQwoFcUeS8+p97c325ud8P6bnkqP3Ow9SerVs
A271tfT+nrv/b5CHjp+Z4wLEEUnmcRuQttc3d+sbTMd0O8AiXZGD79Md0CFfVtEM
6M3TUfMONObP5t+/1K43tFu6pucVRLHZzlcV8zfFeUOAOzBaVZ5lpYXM5amCUO41
Yeo+kUcaF0mKcSzB6L2QDpcQiJGDnoWfqFvwpB/N88R4aqB9Kb5+ihAEibCqzscI
nposQgUAA9+Ght4xY1ZC0weMPa9zWy10zu4RtjLW/5RzA4KbpeD/eqkcX2KHRHQD
ZWS3yc4MZ2StPeQMRd9BXPOkfPy+CtsfVlhNpJ1AgBhcZFo1nhs+Ng1WH1oR2Rad
m5iM0dMX/vMKDNK8LuQ7Uy54HbJzTKlwfo+q0Pf5K/saLBRGDO3z8DyDMgMzVFmD
wXaLlhrGzTUsi7jGBbAvB7E8z1OAH+QWH2R1Fw3zzD9o0iiS6xvC5c4lEGG+jG83
YpOseoiFhIoiB7OPCRAr4n1H2FhwhmGYfP/zOR8qcp3eMXy0GsPVdygwoGg1MV32
4XtWiEnf/HKN2zmJ1MYBcQ==
=FnBp
-----END PGP SIGNATURE-----