team upload rules

[Hefee]

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.

>   - 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.

Regards,

hefee
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-talk/attachments/20241207/a420b034/attachment.sig>