Jump to: navigation, search

Difference between revisions of "Meetings/QATeamMeeting"

(Weekly QA Team meeting)
(Agenda for next Office hours: Updates for 2024.2, drop old eom branches in queries)
 
(886 intermediate revisions by 66 users not shown)
Line 1: Line 1:
 +
__TOC__
  
 
= Weekly QA Team meeting =
 
= Weekly QA Team meeting =
The OpenStack QA Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, '''Thursday at 1:00 EDT (17:00 UTC)'''.<br />
+
The [[QA|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.
Everyone interested in testing, quality assurance, performance engineering, etc, should attend!
 
  
== Proposed Agenda for June 20 2013 ==
+
The [[QA|OpenStack Quality Assurance (QA)]] team holds public weekly Office hours:
* Blueprints
+
* Channel:  <code><nowiki>#openstack-qa</nowiki></code>
* Critical Reviews
+
* Time:
* Testr Progress
+
** Tuesdays biweekly at 15:00 UTC (even weeks, starting week 46, 2023)
* Stress Tests in CI
+
** Wednesday biweekly at 17:00 UTC (odd weeks, starting week 45, 2023)
* Testing Multiple Versions of API
+
* ical - http://eavesdrop.openstack.org/#QA_Team_Office_hours
  
== Proposed Agenda for June 13 2013 ==
+
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]
  
* Blueprints?
+
'''''Rules for adding to the agenda''''':
* Critical Reviews?
+
* anyone is free to add to proposed agenda, please do so by 1 hr before the Office hours
* Open Discussion
+
* 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
 
 
 
 
== Previous meetings ==
 
  
All previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/qa/.
 
  
=== Agenda of last meeting June 6 2013 ===
+
'''''Tips to Chair the Office hours''''':
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-06-06-17.00.html meeting minutes for June 6 on eavesdrop].''
+
* 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
  
* Bug Day Roundup
+
== Agenda for next Office hours ==
** http://status.openstack.org/bugday/
+
PING LIST-
* Blueprints
+
* Announcement and Action Item (Optional)
** https://launchpad.net/tempest/+milestone/havana-2
+
* Priority Items progress
** Quantum blueprints consolidated
+
** go through the 2024.2 priority items list and try to plan the work / highlight milestones
* Critical reviews
+
*** https://etherpad.opendev.org/p/qa-dalmatian-priority
** Please provide links
+
* OpenStack Events Updates and Planning (Optional)
* QA Docs
+
** <This includes the OpenStack Summit and PTG updates and planning>
** at http://docs.openstack.org/developer/tempest/
+
* Gate Status / Fix Checks
* Tempest/Flake8/testr issues
+
** <not just QA projects gate but any other project gate also where QA team can help>
** http://lists.openstack.org/pipermail/openstack-qa/2013-May/000429.html
+
** Gate Blocker Fix / Urgent Change
** https://jenkins.openstack.org/job/gate-tempest-pep8/3549/consoleText
+
*** 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
 +
*** #info STOP DOING BARE RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures
 +
* 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)
 +
* Periodic jobs Status Checks
 +
** Periodic stable full: https://zuul.openstack.org/builds?pipeline=periodic-stable&job_name=tempest-full-2023-1&job_name=tempest-full-2023-2&job_name=tempest-full-2024-1
 +
** Periodic stable slow: https://zuul.openstack.org/builds?job_name=tempest-slow-2024-1&job_name=tempest-slow-2023-2&job_name=tempest-slow-2023-1
 +
** Periodic extra tests: https://zuul.openstack.org/builds?job_name=tempest-full-2024-1-extra-tests&job_name=tempest-full-2023-2-extra-tests&job_name=tempest-full-2023-1-extra-tests
 +
** 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
 +
** Debian: https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bullseye&job_name=devstack-platform-debian-bookworm&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&job_name=devstack-platform-openEuler-22.03-ovs&skip=0
 +
** jammy: https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-jammy-ovn-source&job_name=devstack-platform-ubuntu-jammy-ovs&skip=0
 +
* Sub Teams highlights (Sub Teams means individual projects under QA program)
 +
** Tempest: https://review.openstack.org/#/q/project:openstack/tempest+status:open
 +
** Patrole: https://review.openstack.org/#/q/project:openstack/patrole+status:open
 +
** Devstack: https://review.openstack.org/#/q/project:openstack/devstack+status:open
 +
** Grenade: https://review.openstack.org/#/q/project:openstack/grenade+status:open
 +
** Hacking: https://review.opendev.org/#/q/project:openstack/hacking+status:open
 
* Open Discussion
 
* Open Discussion
 +
** [everyone feel free to add their topics under Open Discussion prior to the Office hours with your irc nickname]
  
=== Agenda of May 30 2013 ===
+
* Bug Triage (last 30 min)
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-05-30-17.05.html meeting minutes for May 30 on eavesdrop].''
+
** https://etherpad.openstack.org/p/qa-bug-triage-dalmatian
  
* Blueprint check in for everyone with H1 blueprints
+
== Previous meetings ==
** https://launchpad.net/tempest/+milestone/havana-1
+
* All previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/qa/.
** move out non landed blueprints
+
* Old agendas are stored on [[Meetings/QATeamMeeting/OldAgendas]]
* Blueprint check in for H2 blueprints
 
** Note, particular focus on Quantum blueprints which seem largely stalled
 
** Quantum blueprint consolidation
 
* Critical reviews tied to blueprints
 
** https://launchpad.net/tempest/+milestone/havana-1 (anything in needs review state)
 
** if you want your reviews considered high priority, please have them attached to blueprints or targeted bugs
 
* QA Docs
 
** at http://docs.openstack.org/developer/tempest/
 
* Open Discussion
 

Latest revision as of 15:19, 30 April 2024

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