Remove team diversity tags note in README

In this commit(https://review.openstack.org/#/c/579870/) removed
diversity tags, it should also be updated here.

Change-Id: Ib2de46cb9325b27f2c5558e5b125080bc732a122
This commit is contained in:
zhangbailin 2018-08-10 12:07:12 +08:00
parent 1bac78965a
commit ec1049c234

View File

@ -6,8 +6,7 @@ Team and repository tags
:target: https://governance.openstack.org/tc/reference/tags/index.html :target: https://governance.openstack.org/tc/reference/tags/index.html
:alt: The following tags have been asserted for the Glance Specifications :alt: The following tags have been asserted for the Glance Specifications
repository: repository:
"project:official", "project:official".
"team:diverse-affiliation".
Follow the link for an explanation of these tags. Follow the link for an explanation of these tags.
.. NOTE(rosmaita): the alt text above will have to be updated when .. NOTE(rosmaita): the alt text above will have to be updated when
additional tags are asserted for glance-specs. (The SVG in the additional tags are asserted for glance-specs. (The SVG in the
@ -51,7 +50,7 @@ Prior to the Juno development cycle, this repository was not used for spec
reviews. Reviews prior to Juno were completed entirely through Launchpad reviews. Reviews prior to Juno were completed entirely through Launchpad
blueprints:: blueprints::
http://blueprints.launchpad.net/glance https://blueprints.launchpad.net/glance
Please note, Launchpad blueprints are still used for tracking the Please note, Launchpad blueprints are still used for tracking the
current status of blueprints. For more information, see:: current status of blueprints. For more information, see::
@ -60,7 +59,7 @@ current status of blueprints. For more information, see::
For more information about working with gerrit, see:: For more information about working with gerrit, see::
http://docs.openstack.org/infra/manual/developers.html#development-workflow https://docs.openstack.org/infra/manual/developers.html#development-workflow
To validate that the specification is syntactically correct (i.e. get more To validate that the specification is syntactically correct (i.e. get more
confidence in the Jenkins result), please execute the following command:: confidence in the Jenkins result), please execute the following command::