/
2019-04-16 3.6 Bug Triage meeting notes

2019-04-16 3.6 Bug Triage meeting notes

Date

Apr 16, 2019

Participants

  • @Sam Im (Deactivated)

  • @Joanna Bebak (Deactivated)

  • @Joanna Szymańska (Deactivated)

  • @Sebastian Brudziński

  • @Wesley Brown

  • @Ashraf

  • @Clay Crosby (Unlicensed)

  • @Douglas Khumalo (Unlicensed)

  • @Matthew Kumbuyo (Deactivated)

Goals

  •  

Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

 

 

@Joanna Bebak (Deactivated)

  • As of now, we have not started testing the 3.6 release candidate 1.

  • We do have one bug that has been found that is a lower priority OLMIS-6201. This is a bug that was created on Monday, but was not a blocker or critical to fix before releasing 3.6

  • Testing process for 3.6 is here: The 3.6 Regression and Release Candidate Test Plan

  • Every person testing should remember to assign themselves to the test case they are executing so no one else picks it up.

  • @Joanna Bebak (Deactivated) will notify everyone on the QA slack channel when the test cycle is available and everyone can start testing.

  • Report all the bugs that you find so that we can review them during the bug triage meeting.

 

@Wesley Brown Is anyone on Team Ona going to assist in testing? How do you keep track of the test cases that are done, and statuses of each? Is it possible to create a version on Confluence so we can add them to the

@Clay Crosby (Unlicensed) Yes, Team Ona is going to use existing data in test to test reporting.

@Sebastian Brudziński will notify the Malawi slack channel when the environment is ready to start testing. Nikodem is currently working on the release.

 









Action items

Decisions

Related content

OpenLMIS: the global initiative for powerful LMIS software