Jump to: navigation, search

Difference between revisions of "Meetings/QATeamMeeting"

(Proposed Agenda for May 16 2013 meeting)
m (Agenda for next Office hours)
(890 intermediate revisions by 66 users not shown)
Line 1: Line 1:
 +
__TOC__
  
= Weekly 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). Everyone interested in testing, quality assurance, performance engineering, etc, should attend!
+
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.
  
= Proposed Agenda for May 16 2013 meeting =
+
The [[QA|OpenStack Quality Assurance (QA)]] team holds public weekly Office hours:
* Blueprint check in for everyone with H1 blueprints
+
* Channel:  <code><nowiki>#openstack-qa</nowiki></code>
** https://launchpad.net/tempest/+milestone/havana-1
+
* Time:
** Note, particular focus on Quantum blueprints which seem largely stalled
+
** Tuesdays biweekly at 15:00 UTC (even weeks, starting week 46, 2023)
** Quantum blueprint consolidation
+
** Wednesday biweekly at 17:00 UTC (odd weeks, starting week 45, 2023)
** What blueprints move out?
+
* ical - http://eavesdrop.openstack.org/#QA_Team_Office_hours
* Critical reviews tied to blueprints
+
 
** https://launchpad.net/tempest/+milestone/havana-1 (anything in needs review state)
+
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]
** if you want your reviews considered high priority, please have them attached to blueprints or targeted bugs
+
 
* QA Docs
+
'''''Rules for adding to the agenda''''':
** Initial docs job added, website publish will happen on commits
+
* anyone is free to add to proposed agenda, please do so by 1 hr before the Office hours
* Discussion on Tags
+
* 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
** Guidelines and expected usage for 'smoke' tests
+
 
** Additional functional tags
+
 
 +
'''''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-
 +
* Announcement and Action Item (Optional)
 +
* Priority Items progress
 +
** go through the zed priority items list and try to plan the work / highlight milestones
 +
*** https://etherpad.opendev.org/p/qa-caracal-priority
 +
* OpenStack Events Updates and Planning (Optional)
 +
** <This includes the OpenStack Summit and PTG updates and planning>
 +
** Summit & PTG
 +
*** the next PTG is gonna be held virtually, April 8-12, 2024
 +
**** etherpad: https://etherpad.opendev.org/p/apr2024-ptg-qa
 +
**** framadate: https://framadate.org/pklG59pH47w6ZdJI (vote for the time of the PTG session)
 +
* 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
 +
*** #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-yoga&job_name=tempest-full-xena&job_name=tempest-full-zed&job_name=tempest-full-2023-1&job_name=tempest-full-2023-2
 +
** Periodic stable slow: https://zuul.openstack.org/builds?job_name=tempest-slow-2023-2&job_name=tempest-slow-2023-1&job_name=tempest-slow-zed&job_name=tempest-slow-yoga&job_name=tempest-slow-xena
 +
** Periodic extra tests: https://zuul.openstack.org/builds?job_name=tempest-full-2023-2-extra-tests&job_name=tempest-full-2023-1-extra-tests&job_name=tempest-full-zed-extra-tests&job_name=tempest-full-yoga-extra-tests&job_name=tempest-full-xena-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
 +
/devstack+OR+project:openstack/grenade)
 +
* 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]
 +
 +
* Bug Triage (last 30 min)
 +
** https://etherpad.openstack.org/p/qa-bug-triage-caracal
  
= Previous meetings =
+
== Previous meetings ==
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]]

Revision as of 14:55, 19 March 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-

/devstack+OR+project:openstack/grenade)

Previous meetings