On Wed, Mar 21, 2018 at 12:21:12AM -0000, Dimitri John Ledkov wrote: > Before Feature Freeze, I was trying to get mongodb 3.6 building, but ran > out of disk-space on official builders to successfully build it. Thus > one more question - why move to 3.4, when 3.6 is the current stable > series? Maybe it makes sense to skip 3.4 altogether, and go straight for > 3.6? > > Is juju trying to use mongodb 3.4, simply because that is what is stale > and available in bionic universe?
Debian is on 3.4 in experimental and I'm not aware of any 3.6 packaging that is ready. So pushing ahead to 3.6 and maintaining that for five years would be a significant amount of increased work and commitment. It's also well past feature freeze now. If your team wants to take that on, feel free to go ahead but please make sure to coordinate with the release team, Juju upstream and any other stakeholders as appropriate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756432 Title: [FFe] Split out mongodb-server-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1756432/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
