Map release process and identify pain points

kellylee-gds commented 3 years ago

What

Agreed in retro on 10/02/21, we would create a map of our release process including all steps (trigger, process, product updates, documentation, comms). Once we have done this, we will run a retro to identify pain points.

Why

So we can improve the release process.

Who needs to know about this

Developers, Content Designer, Technical Writer, Community Manager, Delivery Manager

Done when

[x] Mapped process
[x] Pain points identified
[x] Solutions identified
[x] Review from team
[x] Documented

trang-erskine commented 3 years ago

https://docs.google.com/document/d/1Jp1qGfXV-YIzeDOJA_6n0MKbO9ijWPhisau46sJmN60/edit#

EoinShaughnessy commented 3 years ago

The content for our release process sits in the govuk-frontend repo.

Do we need to:

relocate this issue to the govuk-frontend repo?
link this issue to the PR for the content update?

trang-erskine commented 3 years ago

Yes we should relocate this to the other repo and link the PR.

alphagov / govuk-frontend