Difference between revisions of "QA"

From Wiki [en] OpenMandriva
Jump to: navigation, search
(Added new section, Policies)
(Communication)
 
(56 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 +
{{Projheader|qa}}
 +
{{Wip}}
  
[[File:Portal_QA.png|center]]
 
  
'''This page is not complete, may not contain accurate information, and most certainly should not be used yet as a guideline until it is announced and verified.''' --[[User:Rxu|Rxu]] ([[User talk:Rxu|talk]]) 15:01, 6 May 2013 (UTC)
 
  
 
== OpenMandriva Quality Assurance ==
 
== OpenMandriva Quality Assurance ==
Line 10: Line 10:
 
The goal of the Quality Assurance group is to ensure not only that bugs do not make their way to the public through testing and standards, but that they may be easily resolved through triaging to their respective packages and maintainers.
 
The goal of the Quality Assurance group is to ensure not only that bugs do not make their way to the public through testing and standards, but that they may be easily resolved through triaging to their respective packages and maintainers.
  
These are not meant to be perfect statements that dictate our work; rather, guiding principles that govern our work. We do not test items like individual packages, as those are left up to the maintainers; rather, we make sure that '''the system as a whole functions properly'''.
+
These are not meant to be perfect statements that dictate our work; rather, guiding principles that govern our work. We do not extensively test items like individual packages, as those are left up to the maintainers (though we do monitor every single update that goes through the system); rather, we make sure that '''the system as a whole functions properly'''.
  
 
  {|align=right
 
  {|align=right
Line 18: Line 18:
 
== Breakdown ==
 
== Breakdown ==
  
* Triaging the information received from sources to those that may find it useful.
 
 
* Cooperating with Cooker maintainers to assign bugs to those that may be able to resolve them.
 
* Cooperating with Cooker maintainers to assign bugs to those that may be able to resolve them.
 
* Providing for the testing repository and ensuring that migration to the stable repositories will not cause harm.
 
* Providing for the testing repository and ensuring that migration to the stable repositories will not cause harm.
 
* Verifying the integrity of standards within the distribution releases.
 
* Verifying the integrity of standards within the distribution releases.
* Coordinating and prioritising major tasks that maintainers need to be aware of.
+
* Coordinating and prioritizing major tasks that maintainers need to be aware of.
 
* Determining, with the help of Cooker maintainers, the release priorities and criteria that must be upheld for any release to happen.
 
* Determining, with the help of Cooker maintainers, the release priorities and criteria that must be upheld for any release to happen.
  
 +
== Joining QA ==
  
== Organising Members ==
+
We welcome everyone to help us test OpenMandriva Lx! You can see our [[QA/Getting_Started|Getting Started]] page for more information about the tools we have at our disposal, and future plans.
  
Those that make the decisions.
+
== Active Members ==
  
* Robert Xu
 
 
* Ben Bullard
 
* Ben Bullard
 
* Colin Close
 
* Colin Close
 
* Chris Tanner
 
* Chris Tanner
 +
* Cristina
  
 +
''(Is this accurate? Speak up people!)''
  
 
== Policies ==
 
== Policies ==
  
You may also want to review [[Cooker/Policies|Cooker's policies]], in addition to ours.
+
QA-Team members need a thorough understanding of:
 +
* [[OpenMandriva_Release_Plan_and_Repositories|Release Plan and Repositories]]
 +
* [[Policies/Repository_Policies|Repository Policies]]
 +
* [[:Category:Releases|Current and Future Releases (including Release Plans)]]
  
* [[QA/Release|Release Criteria and Decisions]]
+
''(There will be more as we better document our distro but we like to keep documentation as simple and light as possible.)''
* [[QA/TestingRepositories|Testing Updates Repositories]]
+
* [[QA/Bugzilla|Bugzilla]]
+
* [[QA/PreRelease|PreRelease Roles]]
+
  
 
== Tools ==
 
== Tools ==
  
 +
We use a variety of tools to help us with our work. However, none compare to the actual task of checking by hand and doing it with actual computers, as those are the true use cases. We invite everyone to test any OpenMandriva official releases that occur, including development and milestone releases.
  
 +
* [http://issues.openmandriva.org OpenMandriva Issue Tracker]
 +
* [https://abf.openmandriva.org/projects ABF]
 +
* [https://github.com/OpenMandrivaSoftware Github]
 +
* [https://kahinah.rxu.tech/ Kahinah]
 +
* Your Brain.
 +
* Your Computer/Computers.
 +
 +
: Please read: [[How to report a bug]]
  
 
== Communication ==
 
== Communication ==
  
We can be found at the '''om-qa''' mailing list. You may subscribe or view the archives from the [http://ml.openmandriva.org OpenMandriva mailing list interface].
+
QA Team daily communication takes place on Freenode IRC channel #openmandriva-cooker but remember that this is also where developers work so mind your IRC manners. Currently OpenMandriva contributor group is small enough that developers and QA work together on IRC. There is also a dedicated [https://forum.openmandriva.org/c/en/qa QA Forum].
 +
 
 +
== Meetings ==
 +
 
 +
QA Team members are encouraged to actively attend weekly TC-Meetings or if unable to attend to read the [https://chwido.openmandriva.org/?dir=meetings/openmandriva-cooker meeting logs] to keep up with what is happening. TC meetings are announced [https://forum.openmandriva.org/t/events-and-meetings-calendar/2735 here]. TC-Meetings take place on Freenode IRC @ #openmandriva-cooker.
 +
 
 +
 
 +
[[Category:QA]]

Latest revision as of 18:23, 18 August 2019

G4217.png


Wip36.png
This article is currently work in progress


OpenMandriva Quality Assurance

Welcome to the OpenMandriva Quality Assurance portal. As our association grows, we strive to ensure that we uphold the standards of the distribution as a whole.

The goal of the Quality Assurance group is to ensure not only that bugs do not make their way to the public through testing and standards, but that they may be easily resolved through triaging to their respective packages and maintainers.

These are not meant to be perfect statements that dictate our work; rather, guiding principles that govern our work. We do not extensively test items like individual packages, as those are left up to the maintainers (though we do monitor every single update that goes through the system); rather, we make sure that the system as a whole functions properly.

Breakdown

  • Cooperating with Cooker maintainers to assign bugs to those that may be able to resolve them.
  • Providing for the testing repository and ensuring that migration to the stable repositories will not cause harm.
  • Verifying the integrity of standards within the distribution releases.
  • Coordinating and prioritizing major tasks that maintainers need to be aware of.
  • Determining, with the help of Cooker maintainers, the release priorities and criteria that must be upheld for any release to happen.

Joining QA

We welcome everyone to help us test OpenMandriva Lx! You can see our Getting Started page for more information about the tools we have at our disposal, and future plans.

Active Members

  • Ben Bullard
  • Colin Close
  • Chris Tanner
  • Cristina

(Is this accurate? Speak up people!)

Policies

QA-Team members need a thorough understanding of:

(There will be more as we better document our distro but we like to keep documentation as simple and light as possible.)

Tools

We use a variety of tools to help us with our work. However, none compare to the actual task of checking by hand and doing it with actual computers, as those are the true use cases. We invite everyone to test any OpenMandriva official releases that occur, including development and milestone releases.

Please read: How to report a bug

Communication

QA Team daily communication takes place on Freenode IRC channel #openmandriva-cooker but remember that this is also where developers work so mind your IRC manners. Currently OpenMandriva contributor group is small enough that developers and QA work together on IRC. There is also a dedicated QA Forum.

Meetings

QA Team members are encouraged to actively attend weekly TC-Meetings or if unable to attend to read the meeting logs to keep up with what is happening. TC meetings are announced here. TC-Meetings take place on Freenode IRC @ #openmandriva-cooker.