...
Make a release page by copying one such as https://confluence.renalregistry.nhs.uk/display/RR/1.1.11 and modifying the Jira component to return tickets from the new version. Blank the release date.
The steps are -
1) While in the branch folder Tag the branch with -
| Code Block |
|---|
rr_git.py --action tagbranch --branch-label Y.Y.Y --tag-label vY.Y.Y |
Y.Y.Y here should be the version being released.
| Note |
|---|
Git, or at least the version of Git on my PC breaks if a tag and branch exist with the same names. This is why I have the tag labels prefixed with a 'v'. |
2) Create a Pull Request for the branch in BitBucket and merge it into Master
3Create a Pull Request for the branch for each of the components in BitBucket and merge it into Master. Do not tick the option to delete the branch.
| Note |
|---|
TODO: rr_git should have a command to do this. |
2) Checkout Master into a new directory with
| Code Block |
|---|
rr_git.py --destination C:/MyWork/UKRR/Master |
| Warning |
|---|
Despite not supplying branch_label this seems to clone the sub-packages using the branch ID from the requirements.txt files. Make sure to checkout master in each directory before doing the next actions. It also seems not to work if the output directory already exists. In this situation a "pull" is also required. |
(Amend path as required)
4) Remove references to the branch from the requirements.txt in the repos under the master folder.
...
Push afterwards.
Note that this requires requires
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
3) Tag the branch with -
| Code Block |
|---|
rr_git.py --action tag --tag-label vY.Y.Y --destination C:/MyWork/UKRR/Master |
Y.Y.Y here should be the version being released.
| Note |
|---|
Git, or at least the version of Git on my PC breaks if a tag and branch exist with the same names. This is why I have the tag labels prefixed with a 'v'. |
5) A new build should have been made under
...