Jump to: navigation, search

Difference between revisions of "Meetings/QATeamMeeting"

Line 47: Line 47:
 
Review pending
 
Review pending
 
  1. https://review.opendev.org/#/c/696068/
 
  1. https://review.opendev.org/#/c/696068/
 +
2. https://review.opendev.org/#/c/699160/ Deprecation of verify-tempest-config
  
 
irc nickname:- kopecmartin
 
irc nickname:- kopecmartin

Revision as of 14:06, 18 December 2019

Weekly QA Team meeting

The OpenStack Quality Assurance (QA) team Develop, maintain, and initiate tools and plans to ensure the upstream stability and quality of OpenStack, and its release readiness at any point during the release cycle.

The OpenStack Quality Assurance (QA) team holds public weekly Office hours:

Everyone interested in testing, quality assurance, performance engineering, etc, should attend! The meeting minutes of previous meetings can be found here: meeting minutes on eavesdrop

Rules for adding to the agenda:

  • anyone is free to add to proposed agenda, please do so by 1 hr before the Office hours
  • if you add an item to the agenda, please include your ircnick (i.e. sdague) to the end of your item, so we know who did, and who should lead the discussion


Tips to Chair the Office hours:

  • Start this meeting using: #startmeeting qa
  • If nothing much to discuss then we can always finish Office hours any time before 1 hour.
  • Announcement and Priority Items progress (first 2 items of Agenda) can be skipped and need not to be tracked every week.

Agenda for next Office hours

PING LIST-

irc nickname:- soniya29 Review pending

1. https://review.opendev.org/#/c/696068/
2. https://review.opendev.org/#/c/699160/ Deprecation of verify-tempest-config

irc nickname:- kopecmartin

Review pending (tempest-cleanup related)
 1. https://review.opendev.org/#/c/693818/ Delete regions
 2. https://review.opendev.org/#/c/694064/ Tempest cleanup: improve iterating over projects
 3. https://review.opendev.org/#/c/698610/ Add tempest-cleanup ansible role
LP: https://bugs.launchpad.net/tempest/+bug/1856671 Smoke test fails when the external network has multiple IPv4 subnets
 * discussion if the condition for just one subnet present is still required

Previous meetings