...
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 Create a Pull Request for the branch folder Tag the branch with -for each of the components in BitBucket and merge it into Master.
| Note |
|---|
TODO: rr_git should have a command to do this. |
2) Checkout Master into a new directory with
| Code Block |
|---|
rr_git.py --action tagbranchdestination C:/MyWork/UKRR/Master |
(Amend path as required)
| Code Block |
|---|
rr_git.py --branch-label Y.Y.Yaction tag --tag-label vY.Y.Y |
3) While in the branch folder Tag the branch with -
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'. |
...
. |
...
| Note |
|---|
TODO: rr_git should have a command to do this. |
3) Checkout Master into a new directory with
| Code Block |
|---|
rr_git.py --destination C:/MyWork/UKRR/Master |
...
4) Remove references to the branch from the requirements.txt in the repos under the master folder.
...