3.17 QA Release & Bug Triage status

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

Bug Triage team

Members

Responsibilities

Notes

Members

Responsibilities

Notes

@Aleksandra Hinc

@Artur Lebiedziński

@Maciej Grochalski

@Krzysztof Pokrywka

  • Review list of bugs provided by @Aleksandra Hinc  in QA slack channel (see query below):

    • Only bugs that have been entered and labeled 3.17RC1bug or 3.17RC2bug 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;

  • Aleksandra will create test cycles for retesting if needed;

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

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

  • We'll meet every two days a week (3 PM) 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:

    • @Aleksandra Hinc

       is responsible for communicating the test plan and bug status in the QA Slack channel.

 

3.17 RC1 bugs:

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

3.17 RC2 bugs:

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

OpenLMIS: the global initiative for powerful LMIS software