Jump to: navigation, search

Difference between revisions of "Meetings/QATeamMeeting"

(Agenda for next Office hours)
(Weekly QA Team meeting)
 
(87 intermediate revisions by 8 users not shown)
Line 6: Line 6:
 
The [[QA|OpenStack Quality Assurance (QA)]] team holds public weekly Office hours:
 
The [[QA|OpenStack Quality Assurance (QA)]] team holds public weekly Office hours:
 
* Channel:  <code><nowiki>#openstack-qa</nowiki></code>
 
* Channel:  <code><nowiki>#openstack-qa</nowiki></code>
* Time: Thursday every week at 00:00 UTC.
+
* Time: Tuesday every week at 14:00 UTC.
 
* ical - http://eavesdrop.openstack.org/#QA_Team_Office_hours
 
* ical - http://eavesdrop.openstack.org/#QA_Team_Office_hours
  
Line 20: Line 20:
 
* If nothing much to discuss then we can always finish Office hours any time before 1 hour.
 
* 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.
 
* Announcement and Priority Items progress (first 2 items of Agenda) can be skipped and need not to be tracked every week.
 +
* End this meeting using: #endmeeting
  
 
== Agenda for next Office hours ==
 
== Agenda for next Office hours ==
 
PING LIST-  
 
PING LIST-  
 
* Announcement and Action Item (Optional)
 
* Announcement and Action Item (Optional)
* Train Priority Items progress  
+
* Yoga Priority Items progress  
** https://etherpad.openstack.org/p/qa-train-priority
+
** go through the yoga priority items list and try to plan the work / highlight milestones
 +
*** https://etherpad.opendev.org/p/qa-yoga-priority
 
* OpenStack Events Updates and Planning
 
* OpenStack Events Updates and Planning
 
** <This includes the OpenStack Summit and PTG updates and planning>
 
** <This includes the OpenStack Summit and PTG updates and planning>
** Next: Shanghai Summit & PTG
+
** Pain Point Elimination - feel free to add your opinion there (QA project)
*** Summit & PTG Planning: TODO
+
*** https://etherpad.opendev.org/p/pain-point-elimination
*** PTG Schedule: TODO
+
** Summit & PTG
 +
*** PTG etherpad tracking the topics discussed during the latest (Yoga) PTG
 +
**** https://etherpad.opendev.org/p/qa-yoga-ptg
 +
* Gate Status / Fix Checks
 +
** <not just QA projects gate but any other project gate also where QA team can help>
 +
** Gate Blocker Fix / Urgent Change
 +
*** https://review.opendev.org/q/label:Review-Priority%253D%252B2+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade+OR+project:openstack/hacking)
 +
* Periodic jobs Status Checks
 +
** Periodic stable: https://zuul.openstack.org/builds?job_name=tempest-full-xena-py3&job_name=tempest-full-wallaby-py3&job_name=tempest-full-victoria-py3&job_name=tempest-full-ussuri-py3&job_name=tempest-full-train-py3&pipeline=periodic-stable
 +
** Periodic master: https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic
 
* Sub Teams highlights (Sub Teams means individual projects under QA program)
 
* Sub Teams highlights (Sub Teams means individual projects under QA program)
 
** Tempest
 
** Tempest
 
*** https://review.openstack.org/#/q/project:openstack/tempest+status:open
 
*** https://review.openstack.org/#/q/project:openstack/tempest+status:open
 
** Patrole
 
** Patrole
*** Initial implementation for multi-policy support: https://review.openstack.org/#/c/554764/
+
*** https://review.openstack.org/#/q/project:openstack/patrole+status:open
*** Once merged, need to create etherpad to track multiple policy changes
+
** Devstack
** Any other (active sub team will add their status reporting here)
+
*** https://review.openstack.org/#/q/project:openstack/devstack+status:open
* Bug Triage
+
** Grenade
** https://etherpad.openstack.org/p/openstack_qa_tempest_2019_bug_review
+
*** https://review.openstack.org/#/q/project:openstack/grenade+status:open
*** old- https://etherpad.openstack.org/p/QA-Stein-Bug-Triage
+
** Hacking
* Critical Reviews
+
*** https://review.opendev.org/#/q/project:openstack/hacking+status:open
 +
** Changes with Review-Priority == +1
 +
*** https://review.opendev.org/q/label:Review-Priority%253D%252B1+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade+OR+project:openstack/hacking)
 
* Open Discussion
 
* Open Discussion
 
** [everyone feel free to add their topics under Open Discussion prior to the Office hours with your irc nickname]
 
** [everyone feel free to add their topics under Open Discussion prior to the Office hours with your irc nickname]
** This bug https://bugs.launchpad.net/tempest/+bug/1783369 is not seen with Swift but affects testing Ceph RGW; anybody willing to look into it? [gfidente]
+
** (gmann) Turning off the openstack-health service and so does retirement of it?
** Speeding up devstack using python script(s) instead of osc to configure resources in keystone. [clarkb]
+
*** (kopecmartin) I agree with retiring, we don't have resources to fix and maintain that , TripleO CI team is working on TripleO Health which should provide similar functionality
 +
* Bug Triage (last 30 min)
 +
** https://etherpad.openstack.org/p/qa-bug-triage-yoga
  
 
== Previous meetings ==
 
== Previous meetings ==
 
* All previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/qa/.
 
* All previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/qa/.
 
* Old agendas are stored on [[Meetings/QATeamMeeting/OldAgendas]]
 
* Old agendas are stored on [[Meetings/QATeamMeeting/OldAgendas]]

Latest revision as of 12:25, 10 November 2021

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.
  • End this meeting using: #endmeeting

Agenda for next Office hours

PING LIST-

Previous meetings