/
3.5 Release: Time-tracking
3.5 Release: Time-tracking
The page is about listing all actions undertaken during the release and the time that each of them consumes in order to determine which of them take the greatest amount of time, and which of them can be quickened, if possible.
Action | Date started | Date finished | Total business days |
---|---|---|---|
Release RC1 | 29 Nov 2018 | 29 Nov 2018 | 0.5? |
Deploy RC1 to all testing instances | 30 Nov 2018 | 30 Nov 2018 | 0.5? |
Regression testing of RC1 | 30 Nov 2018 | 04 Dec 2018 | 3 |
Deploy to performance test instance and make it run MW data | 28 Nov 2018 | 28 Nov 2018 | 1~2 hour(s) |
Performance testing - RC1 | 06 Dec 2018 | 10 Dec 2018 | 1 |
RC1 Phase 2 Bug fixes | 04 Dec 2018 | 07 Dec 2018 | 4 |
Release RC2 | 07 Dec 2018 | 07 Dec 2018 | 3 hours |
Deploy RC2 to all testing instances | 07 Dec 2018 | 07 Dec 2018 | ? |
Regression testing of RC2 | 10 Dec 2018 | 11 Dec 2018 | 2 |
, multiple selections available,
Related content
3.5 Release Schedule and Responsibilities
3.5 Release Schedule and Responsibilities
More like this
3.5 Regression and Release Candidate Test Plan
3.5 Regression and Release Candidate Test Plan
More like this
Backlog Grooming Sprint 50
Backlog Grooming Sprint 50
More like this
2018-09-24 QA Weekly Meeting notes
2018-09-24 QA Weekly Meeting notes
More like this
Backlog Grooming Sprint 104
Backlog Grooming Sprint 104
More like this
The 3.12 Regression and Release Candidate Test Plan
The 3.12 Regression and Release Candidate Test Plan
More like this
OpenLMIS: the global initiative for powerful LMIS software