Open Stack

Mark McLoughlin wrote:
> If you look at the Oslo "mission statement(s)":
> 
>   https://wiki.openstack.org/wiki/Oslo
> 
>   The Oslo program produces a set of python libraries containing
>   infrastructure code shared by OpenStack projects. The APIs provided by
>   these libraries should be high quality, stable, consistent and
>   generally useful. 
> 
>   The Oslo program brings together generalist code reviewers and
>   specialist API maintainers. They share a common interest in tackling
>   copy-and-paste technical debt across the OpenStack project.
> 
> then the overlap with openstack/requirements isn't at all obvious.
> 
> Not to try and lump this solely on Thierry or anything, but I see this
> as a release/distribution management concern - the fundamental question
> is what external dependencies (and what version of those) is it sane for
> us to require in order to deploy OpenStack?
> 
> Looking again at the review criteria:
> 
>   https://wiki.openstack.org/wiki/Requirements
> 
> those questions are all about keeping a firm control over what external
> risks we expose ourselves (e.g. flakey upstreams) and that the
> dependency is compatible with our release goals (e.g. license, python
> version, distro availability).

+1

Cool, now the "Distribution/ReleaseManagement" program has one repo !
Even two, if I count the openstack-releasing tools :)

That kinda proves that the "should have one repo" requirement doesn't
really make sense for programs.

-- 
Thierry Carrez (ttx)