Hi! I was reading https://lts-team.pages.debian.net/git-workflow-lts.html and have a couple of questions:
1. Why use `debian/.gitlab-ci.yml` instead of `debian/salsa-ci.yml`? 2. Why run `git checkout -b upstream` and not `git checkout -b upstream/latest` as per DEP-14? 3. Why do you delete `debian/gbp.conf` and then pass all gbp configs manually each time? Would it not be much easier to replace the `debian/gbp.conf` with one that includes `debian-branch = debian/stretch` etc lines? 4. Why do you maintain a fork of Salsa CI at https://salsa.debian.org/lts-team/pipeline? Why not submit all pipeline improvements upstream to Salsa CI and instead of https://salsa.debian.org/lts-team/pipeline/raw/master/recipes/buster.yml use https://salsa.debian.org/salsa-ci/pipeline/raw/master/recipes/buster.yml? 5. Are you aware that the RELEASE does not need to be set manually at all? You can just keep the existing debian/salsa-ci.yml in the package and once you add a new changelog entry for stretch/buster/bullseye all the jobs in the CI pipeline will automatically build and test using the release in debian/changelog (only exception being Lintian, which currently always runs the Sid version)? - Otto PS. I am not on this list, please Reply-to-all
