production is where all approved production code with reside.
master is where approved code sits that is awaiting deployment to production, and is deployed to a staging subdomain.
master should always have a green pipeline and any bugs found in the staging process should be immediately addressed.
Developers must take personal responsibility for the stability of their code. This entails working spec tests and smoke testing in the
If a merge requested is not prefixed with
WIP: it is considered ready to go into
master and subsequently
||Assuming that no issues are discovered in
- Tracking of issues. If a merge request closes an issue, it must somehow be clear that it is or is not in production. Need to investigate if labels can help here
stagingneed to be clear. Perhaps a
CD::Staginglabel could work here
If there is a bug in
stagingit should be made clear that merging into
productionshould be halted. Should a merge request be made from
- True/False: This process is a strong as our weakest contributor? Code approvals need to be of a high quality.
We need to keep aligned to our goal of