Merge "Add tag for tempest plugins"

This commit is contained in:
Jenkins
2016-09-13 20:16:55 +00:00
committed by Gerrit Code Review
3 changed files with 60 additions and 0 deletions

View File

@@ -405,6 +405,7 @@ designate:
tags:
- release:independent
- type:library
- type:tempest-plugin
python-designateclient:
repos:
- openstack/python-designateclient
@@ -824,6 +825,7 @@ horizon:
tags:
- type:library
- release:independent
- type:tempest-plugin
xstatic-angular:
repos:
- openstack/xstatic-angular
@@ -5841,6 +5843,7 @@ sahara:
tags:
- release:independent
- type:library
- type:tempest-plugin
sahara-specs:
repos:
- openstack/sahara-specs

View File

@@ -47,6 +47,7 @@ Release Management Tags
type_horizon-plugin
type_library
type_service
type_tempest-plugin
Vulnerability Management Tags
=============================

View File

@@ -0,0 +1,56 @@
::
This work is licensed under a Creative Commons Attribution 3.0
Unported License.
http://creativecommons.org/licenses/by/3.0/legalcode
.. _`tag-type:tempest-plugin`:
=====================
type:tempest-plugin
=====================
This tag is part of the type-classification system for projects
managed by the release team. ``type:tempest-plugin`` indicates that a
deliverable is meant to be consumed by :ref:`project-tempest` as a
plug-in, to provide an unified integration test suite for a given project.
Application to current projects
===============================
.. tagged-projects:: type:tempest-plugin
Rationale
=========
We have a growing number of projects that are Tempest plugins, and it would be
useful to have them easily grouped together. Using this tag will help both users
and automated tooling identify which deliverables provide companion
functionality for Tempest.
Requirements
============
* The repository contains code meant to be dynamically loaded by
Tempest to provide an unified integration test suite for a given project.
Tag application process
=======================
Anyone may propose adding or removing this tag to a set of projects by
proposing a change to the openstack/governance repository. The change
is reviewed by the Release Team and the QA PTL, and the Technical
Committee finally approves it using its lazy consensus approval rule.
Deprecation
===========
There is no deprecation process for tags in the ``type`` namespace. If
we need to change the type of a project, we can just do that.
.. _releases.openstack.org: http://releases.openstack.org/