What's the plan for mongo 3.2 ? Will we be required to support 2.x versions for the foreseeable future, or is there a possibility to make it a build or run time failure if mongo < 3.2 is installed on the host ?
On Wed, May 18, 2016 at 9:01 AM, Martin Packman <martin.pack...@canonical.com> wrote: > On 17/05/2016, Curtis Hovey-Canonical <cur...@canonical.com> wrote: >> >> The juju-mongo2.6 package will be be preferred by juju 1.2.5 in xenial >> and without other changes, 2.4 will be used by all other 1.25 series. > > This isn't yet true, there's a bug open for it: > > "Use juju-mongodb2.6 for 1.25 on xenial" > <https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1570650> > > I had made the packaging change, but without juju code changes as well > it just went and installed the old (2.4) juju-mongodb anyway when > setting up a state server. > > Martin > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
