Jump to: navigation, search

Difference between revisions of "Meetings/QATeamMeeting"

(Agenda for next Office hours)
m (Agenda for next Office hours)
 
(159 intermediate revisions by 12 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 09:00 UTC and 17:00 UTC.
+
* Time: Tuesday every week at 15:00 UTC.
 +
* ical - http://eavesdrop.openstack.org/#QA_Team_Office_hours
  
Everyone interested in testing, quality assurance, performance engineering, etc, should attend! The meeting minutes of can be found here: [http://eavesdrop.openstack.org/meetings/qa meeting minutes on eavesdrop]
+
Everyone interested in testing, quality assurance, performance engineering, etc, should attend! The meeting minutes of previous meetings can be found here: [http://eavesdrop.openstack.org/meetings/qa meeting minutes on eavesdrop]
  
 
'''''Rules for adding to the agenda''''':
 
'''''Rules for adding to the agenda''''':
Line 19: 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- gmann, andreaf, masayukig, chandankumar
+
PING LIST-  
 
* Announcement and Action Item (Optional)
 
* Announcement and Action Item (Optional)
* Rocky Priority Items progress  
+
* Antelope Priority Items progress  
** https://etherpad.openstack.org/p/qa-rocky-priorities-tracking
+
** 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>
** Vancouver Summit
+
** Summit & PTG
*** Forum sessions: http://lists.openstack.org/pipermail/openstack-dev/2018-March/127947.html
+
*** the last PTG was held on October 17-20th 2022 virtually - https://openinfra.dev/ptg/
*** https://etherpad.openstack.org/p/YVR-qa-brainstorming
+
*** PTG etherpad tracking the topics for the Antelope cycle
 +
**** https://etherpad.opendev.org/p/qa-antelope-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)
 +
** 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)
 +
*** #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 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
 +
* 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
 
* 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
*** Feature flag for supporting backwards-incompatible policies for n-1/n-2 testing: https://review.openstack.org/#/c/556136/
+
*** https://review.openstack.org/#/q/project:openstack/patrole+status:open
*** Initial implementation for multi-policy support: https://review.openstack.org/#/c/554764/
+
** Devstack
*** Once merged, need to create etherpad to track multiple policy changes
+
*** https://review.openstack.org/#/q/project:openstack/devstack+status:open
** Any other (active sub team will add their status reporting here)
+
** Grenade
* Bug Triage
+
*** https://review.openstack.org/#/q/project:openstack/grenade+status:open
** http://paste.openstack.org/show/701412/
+
** Hacking
 +
*** 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)
 
* Open Discussion
 
* Open Discussion
** (jlvillal) I recommend a new release of hacking be done. Current hacking is using an old version of 'flake8' and other libraries. The unreleased version of hacking has commit 24d7eb6a40e565d17d06046f847590a472430b3e which has updated it to use the new version of 'flake8' which also means using 'pycodestyle' which is what the 'pep8' library was renamed to.
 
 
** [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]
 +
 +
* Bug Triage (last 30 min)
 +
** 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]]

Latest revision as of 15:11, 29 November 2022

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