tfgrid/circle_engineering
23
0
Fork 0
Code Issues 66 Pull Requests Packages Projects Releases Wiki Activity

3.16 Grid Release Timeline #126

New Issue
Open
opened 2024-11-04 18:50:15 +00:00 by mik-tf · 0 comments
mik-tf commented 2024-11-04 18:50:15 +00:00
Owner
Copy Link

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)
# 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)
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
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
  
Issue

   
Question

   
Roadmap

   
Story

   
Task

   
Urgent
No Label
Issue
Question
Roadmap
Story
Task
Urgent
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
tfgrid_3_16
Assignees
Clear assignees
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.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?