team upload rules
Hefee
hefee at debian.org
Sat Dec 7 17:08:46 GMT 2024
Hey,
as far I know your team policy is, that if we upload to the archive, we should
wait to push until we get an ACK from dak, that the package was accepted.
My personal workflow is nowadays:
* add the commit dch -r
* tag the commit with git tag
* build source pkg
* git push branch
* upload via dput
* wait for ACK
* upload the tag
But the ACK takes sometimes several hours, so I switch to focus on something
else and and later forget about pushing the tag afterwards.
At least for me it is quite sub optimal.
On the other side I'm interest in changes done by others and can't look the
changes, because they haven't pushed yet, because the switched their focus on
something else in meanwhile.
I would like to change the rule to push branch and tag directly if dput was
successful.
I am sure that there are reasons for this rule, but I don't know them.
Can someone give some background for this rule?
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/cb3118a8/attachment.sig>
More information about the pkg-kde-talk
mailing list