team upload rules

[Simon Quigley]

Hello,

On 12/7/24 02:08 PM, Hefee wrote:
> Hey,
> 
>> Pushing the commits should be no problem. In fact, I try to do that as I
>> commit, just so others can stay in sync with me if they'd like.
>   
>> As for the tag, that policy exists to be safe. I'd say 80-90% of the time,
>> if you pushed the tag immediately, you'll be fine. For the other 10-20% of
>> the time, dak rejects it for some reason you aren't immediately aware of.
>> Some of my favorites:
>>   - Missing an orig tarball.
>>    - Missing an asc file in the archive if the orig tarball already exists.
>>    - Missing a binary upload since it needs to hit binary NEW.
> 
> all those three reasons, do not do anything with the tag, as it is "only" the
> way you create the changes file. And you can just recreate the changes with
> with other options.

Right, but if you push a tag, go to do something else, don't see that it was rejected, and forget to go back, the next person will be confused and wonder what happened to that upload.

> 
>>    - Two uploaders try to upload something with the same version number at
>> roughly the same time. dak rejects one of them.
>   
> ACK this one is a valid reason.

Thanks,
-- 
Simon Quigley
simon at tsimonq2.net
@tsimonq2:ubuntu.com on Matrix
tsimonq2 on LiberaChat and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-talk/attachments/20241207/7b1cd5e0/attachment.sig>