Jump to: navigation, search

Difference between revisions of "Meetings/QATeamMeeting"

(Weekly QA Team meeting)
m (Agenda for next Office hours)
(753 intermediate revisions by 65 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: Tuesday every week at 13:00 UTC.
* Testr Progress
+
* ical - http://eavesdrop.openstack.org/#QA_Team_Office_hours
* Stress Tests in CI
 
* Testing Multiple Versions of API
 
  
== 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 ==
+
'''''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.
  
All previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/qa/.
+
== Agenda for next Office hours ==
 
+
PING LIST-
=== Agenda of last meeting June 6 2013 ===
+
* Announcement and Action Item (Optional)
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-06-06-17.00.html meeting minutes for June 6 on eavesdrop].''
+
* Victoria Priority Items progress
 
+
** https://etherpad.opendev.org/p/qa-victoria-priority
* Bug Day Roundup
+
* OpenStack Events Updates and Planning
** http://status.openstack.org/bugday/
+
** <This includes the OpenStack Summit and PTG updates and planning>
* Blueprints
+
** Summit & PTG
** https://launchpad.net/tempest/+milestone/havana-2
+
*** PTG: https://www.openstack.org/ptg/
** Quantum blueprints consolidated
+
*** OCTOBER 19-23, 2020: https://www.openstack.org/summit/2020/
* Critical reviews
+
*** http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016807.html
** Please provide links
+
*** https://etherpad.opendev.org/p/qa-wallaby-ptg
* QA Docs
+
* Sub Teams highlights (Sub Teams means individual projects under QA program)
** at http://docs.openstack.org/developer/tempest/
+
** Tempest
* Tempest/Flake8/testr issues
+
*** https://review.openstack.org/#/q/project:openstack/tempest+status:open
** http://lists.openstack.org/pipermail/openstack-qa/2013-May/000429.html
+
** Patrole
** https://jenkins.openstack.org/job/gate-tempest-pep8/3549/consoleText
+
*** https://review.openstack.org/#/q/project:openstack/patrole+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
 +
* Bug Triage
 +
** https://etherpad.openstack.org/p/qa-bug-triage-victoria
 +
* Critical Reviews
 
* Open Discussion
 
* Open Discussion
 +
** [everyone feel free to add their topics under Open Discussion prior to the Office hours with your irc nickname]
 +
** (TomStappaerts) Devstack does not work on centos8 with stable/ussuri. I backported a fix here: https://review.opendev.org/#/c/746500/ . Are there other actions we need to do?
  
=== Agenda of May 30 2013 ===
+
== Previous meetings ==
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-05-30-17.05.html meeting minutes for May 30 on eavesdrop].''
+
* 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]]
* Blueprint check in for everyone with H1 blueprints
 
** https://launchpad.net/tempest/+milestone/havana-1
 
** move out non landed blueprints
 
* 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
 

Revision as of 12:23, 1 September 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.

Agenda for next Office hours

PING LIST-

Previous meetings