3.16 Grid Release Timeline #126

Open
opened 2024-11-04 18:50:15 +00:00 by mik-tf · 1 comment
Owner

3.16 Grid Release Timeline

We provide the overall guideline for 3.16 grid release. Making sure all those steps are done in order will ensure the 3.16 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
# 3.16 Grid Release Timeline We provide the overall guideline for 3.16 grid release. Making sure all those steps are done in order will ensure the 3.16 grid release is done efficiently. - [x] Stakeholders meet and define the grid release specs - [x] Specs are turned into stories in a grid release project kanban - [x] 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
mik-tf added the
Story
label 2024-11-04 18:50:15 +00:00
mik-tf added this to the tfgrid_3_16 project 2024-11-04 18:50:15 +00:00
mik-tf self-assigned this 2024-12-31 16:57:06 +00:00
Author
Owner

Update

  • All the stories have owners now
  • TODO
    • next stakeholders meeting, go through 3.16 board and confirm everything
    • then comms will write a 3.16 forum post as explained above
# Update - All the stories have owners now - TODO - next stakeholders meeting, go through 3.16 board and confirm everything - then comms will write a 3.16 forum post as explained above
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: tfgrid/circle_engineering#126
No description provided.