Jump to: navigation, search

Difference between revisions of "Meetings/QATeamMeeting"

(Agenda for next Office hours)
(788 intermediate revisions by 70 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: Tuesday every week at 14:00 UTC.
 +
* 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)
 +
* Wallaby Priority Items progress
 +
** https://etherpad.opendev.org/p/qa-wallaby-priority
 +
* OpenStack Events Updates and Planning
 +
** <This includes the OpenStack Summit and PTG updates and planning>
 +
** Summit & PTG
 +
* Gate Status Checks
 +
** <not just QA projects gate but any other project gate also where QA team can help>
 +
* Sub Teams highlights (Sub Teams means individual projects under QA program)
 +
** Tempest
 +
*** https://review.openstack.org/#/q/project:openstack/tempest+status:open
 +
*** (gmann) Need consensus on  https://review.opendev.org/#/c/673342/3
 +
** 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
 +
* Community goal tracking
 +
** https://etherpad.openstack.org/p/qa-community-wide-goals-tracking
 +
* Gate Blocker Fix / Urgent Change
 +
* 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-wallaby
  
https://review.openstack.org/#/q/status:open+project:openstack/tempest,n,z
+
== Previous meetings ==
 
+
* All previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/qa/.
* New items for discussion
+
* Old agendas are stored on [[Meetings/QATeamMeeting/OldAgendas]]
 
 
1. (Jay) Getting some consensus on what precisely a "smoke test" is and
 
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 18:05, 17 November 2020

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