Backlog Grooming Sprint 38

Goal: Take 1 additional week to work on critical performance improvements.

Timeline: Publish a Release Candidate by end of day Tuesday 31 Oct 2017 1 Nov 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.

• https://openlmis.atlassian.net/browse/OLMIS-3318 (#3) (Team Parrot continue, Nick will reach out to discuss)

• https://openlmis.atlassian.net/browse/OLMIS-3346 (#4) (Team ILL will take it on, document, and then share)

• https://openlmis.atlassian.net/browse/OLMIS-3182 (Team ILL - Nick)

• anything else?

• 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)

  • https://openlmis.atlassian.net/browse/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)

  • https://openlmis.atlassian.net/browse/OLMIS-3222 (@Sam Im (Deactivated) will discuss and add details about a small fix and Zephyr edge case)

  • https://openlmis.atlassian.net/browse/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:

  • https://openlmis.atlassian.net/browse/OLMIS-3320 (#9)

    • Q: Do we want to add performance test for /forConvert endpoint?

  • https://openlmis.atlassian.net/browse/OLMIS-3362 (#13) (Team ILL - Nick may have already fixed it; @Sam Im (Deactivated) will add to regression to add a test case)

• Bugs:

  • https://openlmis.atlassian.net/browse/OLMIS-3438

  • https://openlmis.atlassian.net/browse/OLMIS-3396

  • https://openlmis.atlassian.net/browse/OLMIS-3357

  • https://openlmis.atlassian.net/browse/OLMIS-3394

  • https://openlmis.atlassian.net/browse/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

  • Team Parrot (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:

    • https://openlmis.atlassian.net/browse/OLMIS-3450

    • https://openlmis.atlassian.net/browse/OLMIS-3451

• anything else?

During Code Freeze period, we will only allow commits that are for release-critical bug fixes, and we will reject/revert all other commits.

• Manual regression testing

  • see 3.2.1 Regression Test Plan 

• Work only on bugs identified as critical issues for release (approved by Team ILL triage team)

• Publish additional Release Candidates (RC2, RC3, etc only if needed)

• Commits to CHANGELOGs and Release Notes

• Commits that fix code formatting (whitespace, in-line documentation)

• Add and edit code in test/, integration-test/ and contract tests

  • it is okay to add test coverage; but do not delete tests or change existing tests/contracts 

  • Sonar: can we get all our quality gates to pass? This would be mostly changes in tests, not in the code itself.

• Videos and group conversations on topics such as DRY, automated testing, etc.
  
  

  • See Learning Materials

• Manual UI Performance testing (Team ILL)

• Write documentation

• NO: Fix CCE bugs. (Since CCE is not part of 3.2.1 release is it okay to keep working on that component)