openstack/governance
Code Issues Proposed changes

Remove the 'integrated-release' tag

Browse Source 
The 'integrated-release' tag was a legacy tag to ensure the
transition between the "Integrated Release" project model and
the "Big Tent with Tags" project model.

We are far enough into the transition now that we can remove
the legacy tag and look forward.

Notes:
- "Integrated" was mentioned in two project team mission statements
  (Horizon and Release Cycle Management), which means this change
  will require their respective PTLs approvals
- Information about integrated release (in particular the "since"
  cycle) is not lost and can easily be retrieved using the
  april-2015-elections tag

Change-Id: I20c662c812f3a1952f21a4ae1cb677a8ae3db488
This commit is contained in:
Thierry Carrez 2015-07-07 18:52:00 +02:00
parent 684ee9dfb3
commit 9b0328f2b9
3 changed files with 2 additions and 105 deletions

34
reference/projects.yaml

@ -12,8 +12,6 @@ Nova:
projects:
- repo: openstack/nova
tags:
- name: integrated-release
since: austin
- name: tc-approved-release
- name: release:managed
- name: release:at-6mo-cycle-end
@ -38,8 +36,6 @@ Swift:
projects:
- repo: openstack/swift
tags:
- name: integrated-release
since: austin
- name: tc-approved-release
- name: release:managed
- name: release:independent
@ -71,8 +67,6 @@ Glance:
projects:
- repo: openstack/glance
tags:
- name: integrated-release
since: bexar
- name: tc-approved-release
- name: release:managed
- name: release:at-6mo-cycle-end
@ -106,8 +100,6 @@ Keystone:
projects:
- repo: openstack/keystone
tags:
- name: integrated-release
since: essex
- name: tc-approved-release
- name: release:managed
- name: release:at-6mo-cycle-end
@ -153,15 +145,13 @@ Horizon:
service: Dashboard
mission: >
To provide an extensible unified web based user interface for all
integrated OpenStack services.
OpenStack services.
url: https://wiki.openstack.org/wiki/Horizon
tags:
- name: team:diverse-affiliation
projects:
- repo: openstack/horizon
tags:
- name: integrated-release
since: essex
- name: tc-approved-release
- name: release:managed
- name: release:at-6mo-cycle-end
@ -202,8 +192,6 @@ Neutron:
projects:
- repo: openstack/neutron
tags:
- name: integrated-release
since: folsom
- name: tc-approved-release
- name: release:managed
- name: release:at-6mo-cycle-end
@ -211,16 +199,12 @@ Neutron:
- name: type:service
- repo: openstack/neutron-fwaas
tags:
- name: integrated-release
since: kilo
- name: release:managed
- name: release:at-6mo-cycle-end
- name: release:has-stable-branches
- name: type:service
- repo: openstack/neutron-lbaas
tags:
- name: integrated-release
since: kilo
- name: tc-approved-release
- name: release:managed
- name: release:at-6mo-cycle-end
@ -228,8 +212,6 @@ Neutron:
- name: type:service
- repo: openstack/neutron-vpnaas
tags:
- name: integrated-release
since: kilo
- name: tc-approved-release
- name: release:managed
- name: release:at-6mo-cycle-end
@ -299,8 +281,6 @@ Cinder:
projects:
- repo: openstack/cinder
tags:
- name: integrated-release
since: folsom
- name: tc-approved-release
- name: release:managed
- name: release:at-6mo-cycle-end
@ -333,8 +313,6 @@ Ceilometer:
projects:
- repo: openstack/ceilometer
tags:
- name: integrated-release
since: havana
- name: tc-approved-release
- name: release:managed
- name: release:at-6mo-cycle-end
@ -373,8 +351,6 @@ Heat:
projects:
- repo: openstack/heat
tags:
- name: integrated-release
since: havana
- name: tc-approved-release
- name: release:managed
- name: release:at-6mo-cycle-end
@ -406,8 +382,6 @@ Trove:
projects:
- repo: openstack/trove
tags:
- name: integrated-release
since: icehouse
- name: tc-approved-release
- name: release:managed
- name: release:at-6mo-cycle-end
@ -438,8 +412,6 @@ Ironic:
- repo: openstack/coreos-image-builder
- repo: openstack/ironic
tags:
- name: integrated-release
since: kilo
- name: tc-approved-release
- name: release:managed
- name: release:at-6mo-cycle-end
@ -906,7 +878,7 @@ Release cycle management:
irc-channel: openstack-relmgr-office
mission: >
To organize the release cycle and the work necessary to produce coordinated
releases of the integrated components of OpenStack. To collect bugfix
releases of the various components of OpenStack. To collect bugfix
backports and produce stable point releases for the previously-released
branch.
url: https://wiki.openstack.org/wiki/Release_Cycle_Management
@ -953,8 +925,6 @@ Sahara:
projects:
- repo: openstack/sahara
tags:
- name: integrated-release
since: juno
- name: tc-approved-release
- name: release:managed
- name: release:at-6mo-cycle-end

1
reference/tags/index.rst

@ -7,7 +7,6 @@
:glob:
compute_starter_kit
integrated-release
release_independent
release_at-6mo-cycle-end
release_has-stable-branches

72
reference/tags/integrated-release.rst

@ -1,72 +0,0 @@
::
This work is licensed under a Creative Commons Attribution 3.0
Unported License.
http://creativecommons.org/licenses/by/3.0/legalcode
.. _tag-integrated-release:
==================
integrated-release
==================
The integrated-release tag describes projects that were "integrated"
in the previous project structure.
Application to current projects
===============================
The following code repositories would get the proposed tag. Those match the
contents of the Kilo release as decided at the end of the Juno cycle, and
take into account the recent Neutron advanced services code split:
.. tagged-projects:: integrated-release
Rationale
=========
Until the tag taxonomy is sufficiently developed to accurately describe
OpenStack projects, we need to hold on to what we currently have. Therefore,
to ensure a seamless transition between the previous project structure and
the new one, the "integrated release" concept is first imported in the
new tag-based project taxonomy as an initial, frozen tag. When we'll complete
the deconstruction of the single "integrated release" concept into a more
precise set of tags, the integrated-release tag will be discontinued.
For more information on this transition plan, see http://governance.openstack.org/resolutions/20141202-project-structure-reform-spec.html
Requirements
============
* Project must be an "integrated" project in the Kilo development cycle
(under the old project structure rules)
Tag application process
=======================
This tag is frozen: only projects that were "integrated" at the beginning of
the Kilo development cycle are and will be granted the "integrated-release"
tag. There is therefore no need for an addition or removal process.
Deprecation
===========
This tag doesn't have a deprecation period. It is expected to simply be
removed when the deconstruction of the "integrated release" concept will
have been completed.
Attributes
==========
since
-----
This attribute describes the development cycle where the project was first
fully integrated (and therefore the first release name where the project was
included). Example values: folsom, kilo