Release: v5.1.0 - Githubissues

alan-turing-institute / data-safe-haven

https://data-safe-haven.readthedocs.io

BSD 3-Clause "New" or "Revised" License

61 stars 15 forks source link

Release: v5.1.0 #2294

Open craddm opened 16 hours ago

craddm commented 16 hours ago

:white_check_mark: Checklist

Refer to the Deployment section of our documentation when completing these steps.

[x] Consult the data-safe-haven/VERSIONING.md guide and determine the version number of the new release. Record it in the title of this issue.
[x] Create a release branch called e.g. release-v0.0.1
[x] Draft a changelog for the release similar to our previous releases, see https://github.com/alan-turing-institute/data-safe-haven/releases

For patch releases only

[ ] Confirm that the resource to which the patch applies can be successfully deployed

For minor releases and above

[ ] Deploy an SHM from this branch and save a transcript of the deployment logs
Using the new image, deploy a tier 2 and a tier 3 SRE
- [ ] Save the transcript of your tier 2 SRE deployment
- [ ] Save the transcript of your tier 3 SRE deployment
[ ] Complete the Security evaluation checklist from the deployment documentation
[ ] Add the new versions tag as an active build on Read The Docs (You can add as a hidden build, before release, to preview)

For major releases only

[ ] Confirm that a third party has carried out a full penetration test evaluating:
1. external attack surface
2. ability to exfiltrate data from the system
3. ability to transfer data between SREs
4. ability to escalate privileges on the SRD.

Update documentation

[ ] Update supported versions in SECURITY.md
[ ] Update pen test results in VERSIONING.md

:computer: Release information

Version number: _
SHM ID: _
T2 SRE ID: _
T3 SRE ID: _

:deciduous_tree: Deployment problems