Jump to: navigation, search

Difference between revisions of "Meetings/QATeamMeeting"

(Agenda for next Office hours)
(733 intermediate revisions by 64 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!
 
  
''Rules for adding to the agenda'':
+
The [[QA|OpenStack Quality Assurance (QA)]] team holds public weekly Office hours:
* anyone is free to add to proposed agenda, please do so by 1 hr before the meeting
+
* Channel:  <code><nowiki>#openstack-qa</nowiki></code>
* 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
+
* Time: Tuesday every week at 14:00 UTC.
 +
* ical - http://eavesdrop.openstack.org/#QA_Team_Office_hours
  
=== Proposed Agenda for August 22 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 (mtreinish)
 
** testr parallel status (mtreinish)
 
** stress tests (mkoderer)
 
* Critical Reviews (mtreinish)
 
* Heat test merge (afazekas)
 
* Devstack independent tempest usage (afazekas)
 
  
== Previous meetings ==
+
'''''Rules for adding to the agenda''''':
All previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/qa/.
+
* 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
  
=== Agenda for August 15 2013 ===
 
* Blueprints (mtreinish)
 
** testr parallel status (mtreinish)
 
** stress tests (mkoderer)
 
* Critical Reviews (mtreinish)
 
  
=== Agenda for August 8 2013 ===
+
'''''Tips to Chair the Office hours''''':
* Volunteers to run meeting while sdague out (sdague)
+
* Start this meeting using: #startmeeting qa
* Blueprints (sdague)
+
* If nothing much to discuss then we can always finish Office hours any time before 1 hour.
* Critical Reviews (sdague)
+
* Announcement and Priority Items progress (first 2 items of Agenda) can be skipped and need not to be tracked every week.
* Stress tests scope and behaviour, also see reviews on https://review.openstack.org/#/c/39752 (gfidente)
+
* End this meeting using: #endmeeting
* Status of slow heat tests (dkranz)
 
  
=== Agenda of August 1 2013 ===
+
== Agenda for next Office hours ==
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-08-01-16.59.html meeting minutes for July 1 on eavesdrop].''
+
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
  
* Blueprints (sdague)
+
== Previous meetings ==
* Critical Reviews (sdague)
+
* All previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/qa/.
* Call for more Core reviewers (dkranz)
+
* Old agendas are stored on [[Meetings/QATeamMeeting/OldAgendas]]
 
 
=== Agenda of July 25 2013 ===
 
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-07-25-17.00.html meeting minutes for July 25 on eavesdrop].''
 
 
 
* Blueprints (sdague)
 
** Current state of implementation
 
** Stress Tests https://blueprints.launchpad.net/tempest/+spec/stress-tests (mkoderer)
 
* WebDav status codes in nova? Consistently using the 404 or 422 on actions.
 
* Adding test cases with skip attribute vote? Exact rule (afazekas)
 
* py26 compatibility (afazekas)
 
* Consistent reviewing (afazekas)
 
* Critical Reviews (sdague)
 
* Separate heat job and slow tests in general (dkranz)
 
 
 
 
 
===Agenda of July 18 2013 ===
 
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-07-18-17.00.html meeting minutes for July 18 on eavesdrop].''
 
 
 
* Blueprints (sdague)
 
** Havana-2 status check in - https://launchpad.net/tempest/+milestone/havana-2 (sdague .. et al)
 
** Testr Progress - https://blueprints.launchpad.net/tempest/+spec/speed-up-tempest (mtreinish)
 
** Stress Tests (new Blueprint and findings) - https://blueprints.launchpad.net/tempest/+spec/stress-tests (mkoderer)
 
* Mailing list move (voting on moving to -dev) (sdague)
 
* White Box Tests (owner for discussion?)
 
** Should they really be unit tests?
 
** Current state of implementation
 
** Integration in CI
 
** Adding test cases with skip attribute (afazekas)
 
* Critical Reviews (sdague)
 
 
 
=== Agenda of July 11 2013 ===
 
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-07-11-17.03.html meeting minutes for July 11 on eavesdrop].''
 
 
 
* QA Program Business
 
** PTL Nominations close - see if we need to run election
 
** Program Description
 
* Blueprints
 
** Havana-2 status check in - https://launchpad.net/tempest/+milestone/havana-2
 
** Testr Progress - https://blueprints.launchpad.net/tempest/+spec/speed-up-tempest
 
* Critical Reviews
 
* Stress Tests in CI
 
* Full Open Stack networking gate job
 
* New stress tests in tempest --[[User:M-koderer|m-koderer]] ([[User talk:M-koderer|talk]]) 16:36, 11 July 2013 (UTC)
 
 
 
 
 
=== Agenda of June 27 2013 ===
 
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-06-27-17.01.html meeting minutes for June 27 on eavesdrop].''
 
 
 
* ''nothing in Agenda ... only QA as OpenStack Program, QA Leader and testr topics were discussed little bit''
 

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