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.
...
...
@@ -5,7 +8,23 @@
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.
- 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.
...
...
@@ -45,5 +64,8 @@
gbp tag --debian-branch=debian/bullseye
```
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
# (optional) start the build
1. (optional) go start build in jenkins: Debian10/advLigoRTS, Debian11/advLigoRTS
2. 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
