PackageReleaseProcedure.md

@@ -3,17 +3,24 @@
 1. Update src/include/rcgversion.h if necessary and commit.  If this is a dev release, set RCG_VERSION_REL to 0.  If a full release, set to 1.
 1. Update NEWS file if needed.
 1. Commit any changes to master branch
+1. Tag commit with version number.  If there is a '~', change that to an '_'.  Omit any debian package number, usually a dash followed by a number.
 1. Checkout debian/buster branch
 1. Update the branch to the latest version from cds.
-1. Merge in latest source (usually just master)
+1. Import from the master branch with
+    ````
+    gbp import-ref master -u <version> --upstream-tag='%(version)s' --debian-branch=debian/buster
+    ```
 1. Make any needed packaging changes
-1. Update version number in debian/changelog
-```dch```
-1. Make sure new version is released in debian/changelog
-```dch -r buster```
-1. Commit.  
-1. Tag commit with version number.  If there is a '~', change that to an '_'.  Omit any debian package number, usually a dash followed by a number.
-1. Push back to cds.
+1. Update the changelog with
+   ```
+   gbp dch -Rc -N <version>-1+deb10 -D stable --debian-branch debian/buster
+   ```
+1. Tag the debian branch with
+   ```
+   gbp tag --debian-branch=debian/buster
+   ```
+1. Push back to gitlab.
+1. Switch to ```debian/bullseye``` branch
 1. Push tags back to cds.
 1. (optional) go start build in jenkins: Debian10/advLigoRTS
 1. Look for version update in: https://apt.ligo-wa.caltech.edu/debian/buster_status.txt
\ No newline at end of file