Jump to: navigation, search

Difference between revisions of "Meetings/QATeamMeeting"

m (→‎Agenda for next Office hours)
(911 intermediate revisions by 71 users not shown)
Line 1: Line 1:
−
__NOTOC__
+
__TOC__
−
= Weekly team meeting =
 
−
The OpenStack QA Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, Thursday at 13:00 EST (17:00 UTC). Everyone interested in testing, quality assurance, performance engineering, etc, should attend!
 
  
−
= Agenda for next meeting =
+
= Weekly QA Team meeting =
 +
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.
  
−
<pre><nowiki>
+
The [[QA|OpenStack Quality Assurance (QA)]] team holds public weekly Office hours:
−
* Review of last week's action items
+
* Channel:  <code><nowiki>#openstack-qa</nowiki></code>
 +
* Time:
 +
** Tuesdays biweekly at 15:00 UTC (even weeks, starting week 46, 2023)
 +
** Wednesday biweekly at 17:00 UTC (odd weeks, starting week 45, 2023)
 +
* ical - http://eavesdrop.openstack.org/#QA_Team_Office_hours
  
−
<LIST ACTION ITEMS>
+
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]
  
−
* Blockers preventing work from moving forward
+
'''''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
  
−
<LIST BLOCKING ITEMS>
 
  
−
* Outstanding code reviews
+
'''''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
  
−
Review all outstanding code reviews in the queue:
+
== 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
 +
** [everyone feel free to add their topics under Open Discussion prior to the Office hours with your irc nickname]
  
−
https://review.openstack.org/#/q/status:open+project:openstack/tempest,n,z
+
* Bug Triage (last 30 min)
 +
** https://etherpad.openstack.org/p/qa-bug-triage-caracal
  
−
* New items for discussion
+
== Previous meetings ==
−
 
+
* All previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/qa/.
−
1. (Jay) Getting some consensus on what precisely a "smoke test" is and
+
* Old agendas are stored on [[Meetings/QATeamMeeting/OldAgendas]]
−
discussing some code Jay will have pushed that cleans up our "smoke
 
−
test" abilities.
 
−
 
 
−
2. (David) Strategy for maintaining the stable/essex tempest branch:
 
−
  a) How much effort should we put into backports of new tempest tests?
 
−
  b) Should be we gating, or have jenkins jobs for, checkins to stable/essex code?
 
−
 
 
−
3. (Ravi) Status of Swift test development for Tempest
 
−
 
 
−
4. (Ravi) Freezing Diablo/Stable branch as we have Essex/Stable.
 
−
 
 
−
5. (Jay) Can we come to a consensus on the subset of Tempest tests that we
 
−
recommend to the core projects to gate their trunks?
 
−
 
 
−
* Open discussion
 
−
</nowiki></pre>
 
−
 
 
−
= Previous meetings =
 
−
Previous meetings, with their notes and logs, can be found in under [[Meetings/QAMeetingLogs]].
 

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

Retrieved from "https://wiki.openstack.org/w/index.php?title=Meetings/QATeamMeeting&oldid=184556"