Re: Creating a new named official debian repository for OpenStack backports (Uploading all of OpenStack to backports)
On 11/03/14 06:57, Thomas Goirand wrote:
> Hi Debian friends and OpenStack users! :)
>
> For the (OpenStack novice) readers, and more readability, just let me
> note this about OpenStack release names:
>
> * Essex == version 2012.1 (the version currently in Wheezy)
> * Folsom == version 2012.2
> * Grizzly == version 2013.1
> * Havana == version 2013.2 (the current OpenStack stable, released
> last October)
> * Icehouse == version 2014.1 (the "next" OpenStack stable, to be
> released next April)
> * Juno == version 2014.2 (to be released at the end of 2014)
Juno is also a release of Eclipse
http://www.eclipse.org/juno/
>
>
> There's also a problem not only OpenStack itself, but also some of its
> dependencies. For example, oslo-sphinx for Icehouse is incompatible
> with oslo-sphinx for Havana (Python module renamed...), python-wsme
> same, etc.
This is something we encounter in VoIP, too, where upstreams fork their
dependencies and bundle them in their code
My feeling is that if they fork a dependency or become really tightly
coupled with it, maybe they should rename it or import it into their
source tree somehow.
Debian also needs to consider being less strict about such bundled
dependencies: if the forked version has 200 patches against it and is
only used by one other package, maybe there are some cases where we need
to give up anticipating that it will live as a standalone library with
co-ordinated security updates, transitions, etc.
Reply to: