Document release process

[fru-io]

Document release process

[dclear]

@nic-hima : recording with transcript of the Jul 20 release - https://ddev.zoom.us/rec/play/J4-Ef-R6SRGrsWe7xA5YZ4byoROCkCczgl6yUR6-I1HtkURBUMBWGaU0lW6xWgM-YcmuRj92pEqpbp2A.JcPDs58cRq2qSo0S

[nic-hima]

@dclear the above zoom recording link requires a password, and I am at a loss as to how/where to find this password. Please help.

---

I'd also like to point out that in my opinion the current User Stories and Acceptance Criteria for this issue of:

## User stories:
- [ ] As an engineer in the organization I need concise documentation on how to release my code to all environments.

## Acceptance criteria:
- [ ] Documentation outlines release process steps from beginning to end.
- [ ] Documentation outlines where to go to obtain help if a problem surfaces.
- [ ] Documentation outlines management of notifications through statuspage

is rather vague and ambiguous.

I'd also like to point out that each one of the A/C could itself be an issue. ESPECIALLY Documentation outlines release process steps from beginning to end. which is my main concern in regards to ambiguity and vagueness.

[dclear]

@dclear the above zoom recording link requires a password, and I am at a loss as to how/where to find this password. Please help.

https://ddev.zoom.us/rec/share/v8h0LuDJ3FlIXqvz-mSHaIl8Q6bJaaa81SgW_6YOmU7IE5I2naxw6e0YZe_Jeyw7 Password: WwT40O.7