team upload rules

[Aurélien COUDERC]

Le samedi 7 décembre 2024, 18:08:46 UTC+1 Hefee a écrit :
> Hey,

Hi

> 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

One major different with my workflow is that I currently push to salsa (branch+tag) either after dput (if I’m reasonably sure it’ll get accepted) or after ACK (if I have more doubts).

When I tell myself to do-the-right-thing™ I do something closer to your workflow but with pushing the N-1 commit in the branch so that I can fix possible issues and have the actual dch -r commit be the one that holds the tag. With your method, at least for the master branch that are protected on Salsa, you’ll have to push fixes after the dch -r commit and tag whatever state passes dak.

I personally like to have the dch -r commit be the same as the git tag and as the ACCEPTed upload.
Which AFAICT you cannot do in your workflow if you get a reject.


Cheers,
--
Aurélien