Richard Hansen <rhansen@rhansen.org> writes: > For a new package, what should I do once I feel that it is ready to be > uploaded? Should I go ahead and create the project in > salsa.d.o/go-team/packages using dh-make-golang and push the commits > there? Or should I get someone else to review my commits in my > personal namespace before pushing to a new go-team project? For a new project, I'd say just create it and push commits. I recommend submitting to https://salsa.debian.org/newgateway-team/reviews/-/issues before NEW upload. > Also, what's the right procedure for updating an existing package? > Should I: > > * Push the new upstream and debian/sid branches then ask someone to > double check my changes (which might require a force push to fix)? > * Push the upstream branch changes then open a merge request for the > debian/sid changes? > * Open a merge request for the upstream branch, wait for it to be > merged, then open a merge request for debian/sid? > * Something else? I think there are many answers to this, but a social one is "start small and increase with confidence and experience". So I'd suggest start making changes in your personal space and ask for review, and if everything is fine you have learned that this class of change is okay and could push that quicker next time as a team commit. The way Debian handle updating several branches concurrently including upstream branches and pristine-tar branches is messy, and not very GitOps-compatible, and I don't think there really are any established process for this. Simplest is to develop in your own workspace, ask for review and iterate until it is possible to open merge requests. Yes this is a slow and frustrating process. Part of the process is to learn patience, which will help you with anything involving Debian. /Simon
Attachment:
signature.asc
Description: PGP signature