On Mon, 2013-07-01 at 18:46 +0200, Thierry Carrez wrote: > Mark McLoughlin wrote: > >> """ > >> 'OpenStack Programs' are efforts which are essential to the completion > >> of our mission, but which do not produce deliverables included in the > >> common release of OpenStack 'integrated' projects every 6 months, like > >> Projects do. > > > > Hmm, this wasn't what I understood our direction to be. > > > > And maybe this highlights a subtle difference in thinking - as I see it, > > Oslo absolutely is producing release deliverables. For example, in what > > way was oslo.config 1.1.0 *not* a part of the grizzly release? > > > > The idea that documentation isn't a part of our releases seems a bit off > > too. > > I suspect what I call "common release of OpenStack 'integrated' projects > every 6 months" is what you call "server projects" later in the thread. > > We publish a number of things, and a subset of them (which I call "the > integrated release") are released together every 6 months. Oslo > libraries are also released, but on a different cadence. Docs are > released, usually with a slight delay. I call those "deliverables", to > avoid confusion with the first set... > > I think we are on the same line, just not using the term "release" for > the same thing ?
Oslo libraries and docs are very much on the same cadence - as in the true meaning of the word, "rhythm". The fact that, for process reasons, oslo libraries get released a little before the server releases and, for pragmatic reasons, docs get released a little after the server releases changes little in my mind - everyone's working in the same cycle to produce a single, integrated OpenStack product. Cheers, Mark. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev