...
Timeline: Publish a Release Candidate by end of day Wednesday Tuesday 31 Oct 2017 1 Nov 2017 and and begin a code freeze then, conduct full Regression Testing starting 2 Nov 2017, issue additional Release Candidates only if needed, and publish a final Release by end of Sprint 8 November 2017.
...
- Regression Tests will be executed on Monday (even though it's not the official Release Candidate; Sam Im (Deactivated) and Joanna Bebak (Deactivated) will determine who is needed to assist in regression testing).
- Rollover tickets (Team Parrot has 2 In Review and 1 In Progress; Team ILL has 2 In Review and 8 Total roll-overs)
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3351 |
---|
|
(#8) (Need to discuss at Sprint Q&A; Paweł Albecki (Deactivated) do you have a new proposed solution? We can discuss at Q&A) Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3222 |
---|
|
(Sam Im (Deactivated) will discuss and add details about a small fix and Zephyr edge case) Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3254 |
---|
|
(move to Team Parrot; see Review Comments for details about Automated Tests to add back; ask Chongsun Ahn (Unlicensed) if you have questions)
- Performance:
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3320 |
---|
|
(#9)- Q: Do we want to add performance test for /forConvert endpoint?
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3362 |
---|
|
(#13) (Team ILL - Nick may have already fixed it; Sam Im (Deactivated) will add to regression to add a test case)
- Bugs:
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3438 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3396 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3357 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3394 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3404 |
---|
|
(Team Parrot - please propose a suggested error message, since we believe the user will need to delete their requisition and re-initiate later when configured correctly)- Re-Authentication issue during Showcase 24 Oct 2017; it happened on the video screen-sharing during showcase, please see if that issue can be re-produced and if so file it as a bug with Steps to Reproduce (Team Parrot)
- Publish Release Candidate ( will release every component including CHANGELOGs; Team ILL will release Ref-Distro RC1 and Release Notes)
- (make your own tickets for this):
- Release each component with CHANGELOGs, minus CCE components (CCE service and CCE UI do not need to be included) by 1 Nov 2017
- Team ILL:
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3450 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-3451 |
---|
|
- anything else?
During Release Process / Code Freeze (starting 1 Nov 2017 end-of-day)
...