| 2014-06-27 15:47:19 |
Robie Basak |
description |
juju uses distro-info-data to understand what Ubuntu releases exist, falling back to its own knowledge if it is not available. When we open a new development release, the version of juju-core that is copied forward does not know about the release, causing juju-core such as in bug 1314686.
As we work to eliminate these bugs, so that juju-core does not have release names hardcoded, we should also make sure that distro-info-data is always available to juju, so that as we open new releases, juju-core will automatically learn about and be able to use them without having to change juju-core itself.
So we should add a dependency of distro-info (or -data) to juju-core. |
[Impact]
Juju in a particular release is expected to deploy future releases unless something fundamental has changed about them. Without having distro-info installed, a user would need to wait for an SRU to juju-core's hardcoded defaults, which we don't want to have to do.
[Development Fix]
Depend on distro-info. Juju automatically sees this and uses its information over its hardcoded defaults (which are necessary on other platforms that do not have distro-info available).
[Stable Fix]
Same as development fix.
[Test Case]
There isn't really one currently that can effectively be executed manually, since it involve waiting for a new release. However, there are now dep8 tests which pretend that a future release exists and that Juju works on them. These should be verified to pass. The catch is that for a Trusty SRU, Utopic exists, of course, and Juju 1.18.4 already knows about it. On balance, I think that if the dep8 "future" tests succeed, then this is sufficient to have confidence that Utopic+1 will also work.
[Regression Potential]
A Juju user who previously did not have distro-info installed will switch Juju's source of knowledge of distribution releases. This could cause a change in behavior.
[Original Description]
juju uses distro-info-data to understand what Ubuntu releases exist, falling back to its own knowledge if it is not available. When we open a new development release, the version of juju-core that is copied forward does not know about the release, causing juju-core such as in bug 1314686.
As we work to eliminate these bugs, so that juju-core does not have release names hardcoded, we should also make sure that distro-info-data is always available to juju, so that as we open new releases, juju-core will automatically learn about and be able to use them without having to change juju-core itself.
So we should add a dependency of distro-info (or -data) to juju-core. |
|
