3.9 QA Release & Bug Triage status

3.9 QA Release & Bug Triage status

This page contains all bugs reported for 3.9 release for tracking and status. This page will be used during daily bug triage, and queries must be updated with labels of 3.9RC1bug or 3.9RC2bug.

Bug Triage team

Members

Responsibilities

Notes

Members

Responsibilities

Notes

@Joanna Bebak (Deactivated)

@Sebastian Brudziński

@Wesley Brown

@Ben Leibert

@Dércio Duvane

@Klaudia Pałkowska (Deactivated)

@Paulina Buzderewicz

@Oskar Hinc (Unlicensed)

@Wojciech Buława (Unlicensed)

@Jakub Jakubowski (Deactivated)

  • Review list of bugs provided by @Joanna Bebak (Deactivated) in QA slack channel (see query below):

    • Only bugs that have been entered and labeled 3.9RC1bug or 3.9RC2bug will be reviewed during triage;

  • Prioritize bugs;

  • Communicate which bugs need to be fixed, who is assigned to fix for each team - only bugs prioritized as Blocker or Critical must be fixed;

  • Joanna will create test cycles for retesting if needed;

  • Joanna will provide status update on bug fixes in QA slack channel as needed;

  • Joanna will communicate in Slack the bugs that have been added to the board for the day.

  • Meet every weekday once in the morning (6 AM PST) and a communication on bug triage status at the end of the day;

  • Guidance on bug prioritization is located here: http://docs.openlmis.org/en/latest/contribute/contributionGuide.html#reporting-bugs;

  • If there are bugs found, then we must retest;

  • Communication of the test plan before we start testing for the release:

    • @Joanna Bebak (Deactivated) is responsible for communicating the test plan and bug status in the QA Slack channel.

3.9 RC1 bugs

 

3.9 RC2 bugs

 

OpenLMIS: the global initiative for powerful LMIS software