From 85856b9c5816f29944744736aea87a0fdac50399 Mon Sep 17 00:00:00 2001 From: yann300 Date: Thu, 28 Apr 2022 14:59:18 +0200 Subject: [PATCH] formatting --- release-management.md | 44 +++++++++++++++++++++---------------------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/release-management.md b/release-management.md index 9be0b443c8..c3802da892 100644 --- a/release-management.md +++ b/release-management.md @@ -67,37 +67,37 @@ The release manager is still responsible for ensuring a project is rolled out sm ## check list: - ### pre release planning +### pre release planning - - [ ] create a new project and prioritize issues / bugs with the team lead and according to the current roadmap. - - [ ] check with the team lead if this needs an intermediate release (intermediate release should be 2-3 weeks max). - - [ ] a release kickoff meeting with the team aiming to get input from everyone and modify the project accordingly. - - [ ] 2-3 days span where team members estimate their issues. - - [ ] a release planning meeting where we agree on the release scope (intermediate and/or classic release). - - [ ] after this meeting: all the issues / PR should have been qualified in term of effort and scope. - - [ ] after this meeting: date for feature freeze, QA period, and release date should be set in the project title. +- [ ] create a new project and prioritize issues / bugs with the team lead and according to the current roadmap. +- [ ] check with the team lead if this needs an intermediate release (intermediate release should be 2-3 weeks max). +- [ ] a release kickoff meeting with the team aiming to get input from everyone and modify the project accordingly. +- [ ] 2-3 days span where team members estimate their issues. +- [ ] a release planning meeting where we agree on the release scope (intermediate and/or classic release). +- [ ] after this meeting: all the issues / PR should have been qualified in term of effort and scope. +- [ ] after this meeting: date for feature freeze, QA period, and release date should be set in the project title. - ### coding period +### coding period - - [ ] 10 min after each daily standup where the release manager give an update of the current situation and ETA. - - [ ] release manager should make sure to be aware of the current state of each issues and PRs during the coding period in order to have a better overview of who is working on what and best provide support to all the team members that are involved in the release. +- [ ] 10 min after each daily standup where the release manager give an update of the current situation and ETA. +- [ ] release manager should make sure to be aware of the current state of each issues and PRs during the coding period in order to have a better overview of who is working on what and best provide support to all the team members that are involved in the release. - ### QA preparation - - - [ ] prepare the internal QA document, assign team members. - - [ ] prepare the external beta test document for beta testers. - - [ ] 1 week before QA period, start engaging with beta testers and online. +### QA preparation - ### feature freeze, QA period. +- [ ] prepare the internal QA document, assign team members. +- [ ] prepare the external beta test document for beta testers. +- [ ] 1 week before QA period, start engaging with beta testers and online. - - [ ] publish to remix-beta every day. - - [ ] merge reviewed PRs. - - [ ] a QA open sync meeting where we all do our assigned tasks. +### feature freeze, QA period. - ### post release +- [ ] publish to remix-beta every day. +- [ ] merge reviewed PRs. +- [ ] a QA open sync meeting where we all do our assigned tasks. - - [ ] retrospective meeting. +### post release + +- [ ] retrospective meeting. ## Assignments: