3.18 QA Release & Bug Triage status

3.18 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

@Szymon Rujner

@Artur Lebiedziński

@Maciej Grochalski

 

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

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

  • @Szymon Rujner will create test cycles for retesting if needed;

  • @Szymon Rujner will provide status update on bug fixes in QA slack channel as needed;

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

  • Status of the bugs will be provided on slack channel

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

    • @Szymon Rujner

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

 

3.18 RC1 bugs:

3.18 RC2 bugs:

OpenLMIS: the global initiative for powerful LMIS software