...
Scheduled Releases
A release will typically be produced once all the tickets in the associated sprint are complete.
However, it is likely that Fran Benoy-Deeney about any releases to be made.
Builds from the Bamboo process are available here:
\\rr-bamboo.northbristol.local\<Product>\<Branch Label>\<ISODate.BambooBuildNumber>
When the code is ready to be released,
...
will want the changeover to happen on a particular day to minimise disruption to staff, particularly if some are mid-way through processing files.
To let Fran know what will be in the build go to the Sprint and each of the "Done" tickets. Any which have resulted in a change to the program (so not "don't fix" or "can't reproduce") and make sure that the "Fix Version" is set to this release.
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 Checkpoint the branch with -
| Code Block |
|---|
rr_git.py --tagbranch --branch-label 1.1.11 --tag-label v1.1.11 |
2) Create a Pull Request for the branch in BitBucket and merge it into Master
3) Checkout Master into a new directory with
| Code Block |
|---|
rr_git.py --destination C:/MyWork/UKRR/Master |
(Amend path as required)
4) Remove references to the branch from the requirements.txt in the repos under the master folder.
| Code Block |
|---|
rr_git.py --action update --destination C:/MyWork/UKRR/Master --message "Update requirements.txt" |
Note that this requires
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
5) A new build should have been made under
| Code Block |
|---|
\\rr-bamboo\Registry_Test_Utils\PRODUCT |
| Info |
|---|
This should be identical to the build that is under \\rr-bamboo\Registry_Utils\PRODUCT\BRANCH . I have suggested using the Master build as a check the merge has completed correctly but there may be arguments for the reverse. |
6) Copy the build to R:\registry_utils\<Product>\<Branch>
...
7) Modify R:\registry_utils\
...
PRODUCT\run.bat to
...
change which folder the executable is found in.
8) Update the Release page with the date that it was released.