Jump to: navigation, search

Difference between revisions of "Meetings/QATeamMeeting"

(Agenda for next Office hours)
m (Agenda for next Office hours)
(44 intermediate revisions by 2 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: Tuesday every week at 14:00 UTC.
+
* Time: Tuesday every week at 15:00 UTC.
 
* ical - http://eavesdrop.openstack.org/#QA_Team_Office_hours
 
* ical - http://eavesdrop.openstack.org/#QA_Team_Office_hours
  
Line 25: Line 25:
 
PING LIST-  
 
PING LIST-  
 
* Announcement and Action Item (Optional)
 
* Announcement and Action Item (Optional)
* Yoga Priority Items progress  
+
** OpenStack Elections, PTL Nominations
** go through the yoga priority items list and try to plan the work / highlight milestones
+
*** https://governance.openstack.org/election/
*** https://etherpad.opendev.org/p/qa-yoga-priority
+
* Antelope Priority Items progress  
 +
** go through the zed priority items list and try to plan the work / highlight milestones
 +
*** https://etherpad.opendev.org/p/qa-antelope-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>
** Pain Point Elimination - feel free to add your opinion there (QA project)
 
*** https://etherpad.opendev.org/p/pain-point-elimination
 
 
** Summit & PTG
 
** Summit & PTG
*** PTG etherpad tracking topics to discuss
+
*** the next PTG is gonna be held virtually on March 27-31, 2023 - https://openinfra.dev/ptg/
**** https://etherpad.opendev.org/p/qa-yoga-ptg
+
*** PTG etherpad tracking the topics for the Antelope cycle
*** Doodle for choosing the best time slots
+
**** https://etherpad.opendev.org/p/qa-bobcat-ptg
**** https://doodle.com/poll/a8gakx4ca6zvtuem?utm_source=poll&utm_medium=link
+
*** the last PTG was held on October 17-20th 2022 virtually - https://openinfra.dev/ptg/
**** based on the doodle we have reserved time in: https://ethercalc.openstack.org/8tum5yl1bx43
 
*** the booked slots are 13-15 UTC October 18th and 15-17 UTC October 19th
 
 
* Gate Status / Fix Checks
 
* Gate Status / Fix Checks
 
** <not just QA projects gate but any other project gate also where QA team can help>
 
** <not just QA projects gate but any other project gate also where QA team can help>
 
** Gate Blocker Fix / Urgent Change
 
** 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)
+
*** 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)
 +
** Bare Recheck tracking:
 +
*** https://etherpad.opendev.org/p/recheck-weekly-summary
 +
**** QA is doing 68.42 % of recheck as bare recheck which is not good.
 +
***** update from August 2nd - 33,33%
 +
***** update from November 1st - 14,29%
 +
***** update from November 29th - 18% (out of 28 rechecks)
 +
***** update from January 10th - 18% (out of 158)
 +
*** #info STOP DOING BARE RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures
 
* Periodic jobs Status Checks
 
* 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 stable: https://zuul.openstack.org/builds?job_name=tempest-full-yoga&job_name=tempest-full-xena&job_name=tempest-full-wallaby-py3&job_name=tempest-full-victoria-py3&job_name=tempest-full-ussuri-py3&job_name=tempest-full-zed&pipeline=periodic-stable
 
** Periodic master: https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic
 
** Periodic master: https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic
 +
* Distros check:
 +
** Centos 9: https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=0
 +
** Fedora: https://zuul.openstack.org/builds?job_name=devstack-platform-fedora-latest&skip=0
 +
** Debian: https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bullseye&skip=0
 +
** Focal: https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-focal&skip=0
 +
** Rocky: https://zuul.openstack.org/builds?job_name=devstack-platform-rocky-blue-onyx
 +
** openEuler: https://zuul.openstack.org/builds?job_name=devstack-platform-openEuler-22.03-ovn-source&skip=0
 
* Sub Teams highlights (Sub Teams means individual projects under QA program)
 
* Sub Teams highlights (Sub Teams means individual projects under QA program)
 
** Tempest
 
** Tempest
Line 58: Line 71:
 
*** https://review.opendev.org/#/q/project:openstack/hacking+status:open
 
*** https://review.opendev.org/#/q/project:openstack/hacking+status:open
 
** Changes with Review-Priority == +1
 
** 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)
+
*** 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)
 
* 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]
** (rosmaita) begging for reviews of this devstack patch that addresses intermittent failures in the python-cinderclient gates: https://review.opendev.org/c/openstack/devstack/+/803521 (there's a note on the patch about why we can't use post-config for this)
+
** (gmann) PyPi additional maintainers audit for QA repo
** (gmann) Turning off the openstack-health service and so does retirement of it?
+
*** https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup
 +
*** https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848.html
 +
 
 
* Bug Triage (last 30 min)
 
* Bug Triage (last 30 min)
** https://etherpad.openstack.org/p/qa-bug-triage-yoga
+
** https://etherpad.openstack.org/p/qa-bug-triage-antelope
  
 
== 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]]

Revision as of 12:29, 2 February 2023

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