Thierry Carrez 9400b21680 Introduce the "deliverables" concept
Our current projects.yaml file lists project teams and git
repositories associated to those. However, things we publish
as a single "thing" may be represented by multiple code
repositories. For example, a "neutron" release is actually made
of openstack/neutron and openstack/neutron-*aas. A "sahara"
release is actually made of openstack/sahara, openstack/sahara-extra
and openstack/sahara-image-elements. Those are all tagged at the
same time with the same version number, and published together
as a single "deliverable".

This change proposes to encode this layer in the projects.yaml file.
It also proposes to apply tags to the deliverable level rather than
at git repository level. Tags are meant to apply to things that are
consumed by our users, not to the technical pieces that help us
build those things. Note that for most projects have single-repo
deliverables and won't really look different. See Sahara and Neutron
in the proposed file to see examples of multi-repo deliverables.

Since this introduces a breaking change in the file format, we also
take the opportunity to simplify the YAML format: since tags no
longer have attributes they can be listed as an array rather than
as a dictionary, sparing us the useless "name:" part.

Change-Id: I2aa729d1b4278743a5e99b41178dc2d11b3e1348
2015-07-27 15:23:01 +02:00
_exts Introduce the "deliverables" concept 2015-07-27 15:23:01 +02:00
_static Update sphinx doc formatting and toctrees 2014-05-06 16:45:00 -04:00 Publish the extra ATCs for projects 2015-03-04 18:04:53 -05:00
index.rst Build list of teams from YAML file 2015-02-24 18:15:04 -05:00
reference Update sphinx doc formatting and toctrees 2014-05-06 16:45:00 -04:00
resolutions Update sphinx doc formatting and toctrees 2014-05-06 16:45:00 -04:00