Open Stack

Michael Johnson wrote:
> [...]
> 2. Issue: There is no documentation for how to add a service to
> OpenStack on the OpenStack website any longer and no policy on what it
> means for artifacts transitioning to OpenStack management.
>    a) Historically not all OpenStack services were required to be
> managed via the release team process. It was not a problem for PTLs to
> push tags and publish releases via alternate processes.
>    b) Question raised: Should this change and all OpenStack services be
> required to use the release process?

It is actually a documented requirement for OpenStack projects that 
"releases of OpenStack deliverables are handled by the OpenStack Release 
Management team through the openstack/releases repository. Official 
projects are expected to relinquish direct tagging (and branch creation) 
rights in their Gerrit ACLs once their release jobs are functional."

See 
https://governance.openstack.org/tc/reference/new-projects-requirements.html

The release team delegates release management for some deliverables that 
use different toolchains (tagged "release-management: external" in 
governance) like for example OpenStack Charms. And some deliverables are 
just not released (tagged "release-management: none"). But the default 
is already to have all services follow the release management process.

-- 
Thierry Carrez (ttx)