5. Commit any changes to master branch, then push the master branch
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.
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 tag. If you are doing a DEV release you can pick something like `5.2.1_dev1`, if you are doing a non-dev release `5.2.1` would work.
- 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
7. Checkout debian/buster branch
8. Update the branch to the latest version from cds.
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.
9. For the following gbp commands, make sure the git repo is clean with no changes and no untracked files.
