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.
- Here you need to generate the version identifier. If you are doing a DEV release you should add the dev keyword at the end of the tag. The format is `N.N.N` for standard releases and `N.N.N~devY`
- Some actual examples are `5.2.1` and `5.2.1~dev1`, and the tag would be `5.2.1_dev1` with the '~' replaced.
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.
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.
- If this command locks up, try `--spawn-editor=never`
- The `*-1+*` is the packaging revision, if you are re-releasing with just packaging changes, you can increase the packaging version here.
- You can remove the `-c` from the arguments if you don't want the command to automatically commit the change log. This is useful, when the editor is not spawning correctly.
13. Tag the debian branch with
```
gbp tag --debian-branch=debian/buster
```
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).
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
# Preparation
1. Checkout source branch, usually just master.
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.
- Here you need to generate the version identifier. If you are doing a DEV release you should add the dev keyword at the end of the tag. The format is `N.N.N` for standard releases and `N.N.N~devY`
- Some actual examples are `5.2.1` and `5.2.1~dev1`, and the tag would be
From here, follow the automatic instructions. If using the automatic instructions,
skip the manual instructions.
# automatic instructions
1. edit "auto_deb_release". Set "source_branch" to the branch use to release the source. Typically the source branch should be "master".
2.`./auto_deb_release`. This script will detect problems, like the tag being on the wrong branch, or the release version not matching the tag, or if the tagged version was already packaged etc.
3. If everything looks ok, the script will pop up an editor with the debian/changes file. Edit the items as appropriate. The header and signatures should be correct.
4. save and quit. The script will append the same change notice to all debian branches, tag and push the code automatically.
# Manual instructions
Do the preparation instructions (above) first before doing the manual instructions.
Only use the manual instructions if you skipped the automatic instructions.`5.2.1_dev1` with the '~' replaced.
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.
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.
- If this command locks up, try `--spawn-editor=never`
- The `*-1+*` is the packaging revision, if you are re-releasing with just packaging changes, you can increase the packaging version here.
- You can remove the `-c` from the arguments if you don't want the command to automatically commit the change log. This is useful, when the editor is not spawning correctly.
13. Tag the debian branch with
```
gbp tag --debian-branch=debian/buster
```
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).
