Update PackageReleaseProcedure authored by Ezekiel Dohmen's avatar Ezekiel Dohmen
1. Checkout source branch, usually just master.
1. Pull latest version from cds
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. For the following gbp commands, make sure the git repo is clean with no changes and no untracked files.
1. Import from the master branch with
2. Pull latest version from cds
3. 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.
4. Update NEWS file if needed.
5. Commit any changes to master branch, then push the master branch
6. 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.
7. Checkout debian/buster branch
8. Update the branch to the latest version from cds.
9. For the following gbp commands, make sure the git repo is clean with no changes and no untracked files.
10. Import from the master branch with
```
gbp import-ref master -u <version> --upstream-tag='%(version)s' --debian-branch=debian/buster
```
Replace `<version>` with the version number. Leave '~' characters as they are (don't change to underscore). Don't change the `%(version)s` part of the command. This is a tag template.
1. Make any needed packaging changes
1. Update the changelog with
11. Make any needed packaging changes
12. Update the changelog with
```
gbp dch -Rc -N <version>-1+deb10 -D stable --debian-branch debian/buster
```
If this command locks up, try `--spawn-editor=never`
1. Tag the debian branch with
13. Tag the debian branch with
```
gbp tag --debian-branch=debian/buster
```
1. Push back to gitlab.
1. Switch to `debian/bullseye` branch
1. Cherry-pick any changes to the debian directory of debian/buster into debian/bullseye.
1. Make any other needed packing changes (but consider making them in debian/buster first).
1. Import from the master branch with
14. Push back to gitlab.
15. Switch to `debian/bullseye` branch
16. Cherry-pick any changes to the debian directory of debian/buster into debian/bullseye.
17. Make any other needed packing changes (but consider making them in debian/buster first).
18. Import from the master branch with
```
gbp import-ref master -u <version> --upstream-tag='%(version)s' --debian-branch=debian/bullseye
```
1. Update the changelog with
19. Update the changelog with
```
gbp dch -Rc -N <version>-1+deb11 -D stable --debian-branch debian/bullseye
```
1. Tag the debian branch with
20. Tag the debian branch with
```
gbp tag --debian-branch=debian/bullseye
```
1. Push tags back to gitlab.
1. (optional) go start build in jenkins: Debian10/advLigoRTS, Debian11/advLigoRTS
1. Look for version update in: https://apt.ligo-wa.caltech.edu/debian/buster_status.txt https://apt.ligo-wa.caltech.edu/debian/bullseye_status.txt
\ No newline at end of file
21. Push tags back to gitlab.
22. (optional) go start build in jenkins: Debian10/advLigoRTS, Debian11/advLigoRTS
23. Look for version update in: https://apt.ligo-wa.caltech.edu/debian/buster_status.txt https://apt.ligo-wa.caltech.edu/debian/bullseye_status.txt
\ No newline at end of file