# Grid Release Timeline

## Introduction

Each grid release follows a clearly defined timeline. This ensures all the tasks are done properly.

## Template

Each grid release should have in its project kanban one issue containing the template below, adjusted with the current grid release.

```
# X.YZ Grid Release Timeline

We provide the overall guideline for X.YZ grid release. Making sure all those steps are done in order will ensure the grid release is done efficiently.

- [ ] Stakeholders meet and define the grid release specs
- [ ] Specs are turned into stories in a grid release project kanban
- [ ] Stakeholders confirm the stories as fulfilling the specs and grid release goals (with Grid+stories ETA)
  - Make sure not to add stories in the middle of the sprint
    - If there is a need, it needs to be agreed upon
- [ ] Comms circles write a forum post explaining the specs of the grid release, preparing community members to the grid release GEP
- [ ] Stories are worked on and completed
- When a grid release project is completed (all stories are completed)
  - [ ] Stakeholders meet and review the stories, confirming they are correctly done
  - [ ] A post summarizing the GEP is posted on the forum, written by Ops (Sabrina)
- [ ] When the GEP is passed, devs and ops implement the new features of the grid (e.g. publish to all networks)
- [ ] Comms circle communicate with the community that the grid release is done

```

For an example, see the 3.16 version [here](https://git.ourworld.tf/tfgrid/circle_engineering/issues/126).