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.
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.