Name: Release v0.1.2
Status: In review
Role | Assignee | Notes |
---|---|---|
Owner | Pavish | |
Approver - Project plan | Kriti | Needs to approve project plan |
Contributor - Design | Ghislaine | Creates designs for ‘switching user databases’ |
Contributors - Design review | Sean, Pavish, Kriti (final approval) | Reviews UX design |
Contributor - Frontend | Pavish | Implements frontend for ‘switching user databases’ and works on any critical frontend issue that might come up during the release cycle |
Contributor - Frontend review | Sean | Reviews frontend code |
Contributor - Backend | Dominykas | Ensures ‘switching user databases’ works as expected and works on any crticial backend issue that might come up during the release cycle |
Contributor - Backend review | Mukesh | Reviews backend code |
Contributor - Hiring testing team | Kriti | Hires testing team and creates required communication channels |
Contributor - Managing testing team | Pavish | Organizes/communicates with team for testing the release |
Contributors - Testing plan | Pavish, Mukesh (for installation testing plan) | Comes up with the release testing plan |
Contributors - Testing | Testing team from Upwork | Performs testing |
The plan is more high level, since individual tasks will be tracked using GH issues.
Date | Outcome |
---|---|
2023-04-10 | Work starts. |
2023-04-18 | Design work related to switching user databases is complete. |
2023-04-18 | Backend work related to switching user databases is complete. |
2023-04-25 | Frontend work related to switching user databases is complete. |
2023-04-28 | Work for Installation improvements is merged. See timeline in Installation improvements project. Release branch is created. |
2023-05-01 | Testing is continued as mentioned in Installation improvements. Any issue that comes up during testing will be fixed directly on the release branch. |
2023-05-05 | Fixes for issues raised during testing is complete. |
2023-05-08 | Release process starts. |
2023-05-10 | Release date. |