zydronium/manage.get.gov
1
0
Fork 0
mirror of https://github.com/cisagov/manage.get.gov.git synced 2025-08-04 00:42:16 +02:00
Code Issues Projects Releases Packages Wiki Activity

added documentation and ADR for release schedule

Browse source
This commit is contained in:
Alysia Broddrick 2023-11-02 19:24:47 -07:00
parent d6eccc8da5
commit 4119d24149
No known key found for this signature in database
GPG key ID: 03917052CD0F06B7
2 changed files with 34 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/operations/README.md
View file

@ -43,6 +43,12 @@ For ease of use, you can run the `deploy.sh <sandbox name>` script in the `/src`
Your sandbox space should've been setup as part of the onboarding process. If this was not the case, please have an admin follow the instructions [here](../../.github/ISSUE_TEMPLATE/developer-onboarding.md#setting-up-developer-sandbox).
## Rules for making Stable and Staging Releases
Releases will be made for staging and stable every week starting on the first day of the sprint (Wednesday), with the second release of the sprint occuring halfway through the sprint. With the excpetion of the first time going into production (see below), these releases will NOT have the same code. The release to stable will be the same commit that was tagged for staging one week prior, making stable one week behind staging. Further, this means staging can be up to a week behind the main branch of code.
If a bug fix needs to be made to stable, the code fix branch will need to be branched NOT off of main, but of of the same commit as the most recent stable commit. Then, after PR review, the code will be merged to main and a new release must be made to stable.
## Serving static assets
We are using [WhiteNoise](http://whitenoise.evans.io/en/stable/index.html) plugin to serve our static assets on cloud.gov. This plugin is added to the `MIDDLEWARE` list in our apps `settings.py`.