Hi all, As far as the MongoDB 2.4 to 2.6 transition goes, it is supported upstream[1] as a "binary-compatible “drop-in” upgrade" and application-side compatibility can be checked in advance by running db.upgradeCheckAllDBs() on a 2.6 client connected to the 2.4 server. In that respect, the transition is far less of a problem than the 2.0-to-2.4 transition needed for a Wheezy to Jessie upgrade. That said, I'm in favor of uploading 2.6 to unstable using the mongodb source name (and not mongodb-2.6) and then providing a Jessie backport.
Since we are in the process of upgrading to MongoDB 2.6 at work, I've
rolled out a 2.6.11 package, trying to benefit from the changes done
both in Ubuntu and László's updated package. For anyone interested, the
source (signed with my DD key) is at
https://dmesg.gr/packages/mongodb_2.6.11-0.1.dsc
I've cleaned up the patches, and done some packaging overhaul, including
making hardened buildflags work. The changelog since 2.4.14-3 lists
every change done, although some attribution may be missing (apologies
for that). I've already tested the clients on our infrastructure, and we
will start rolling out the server package soon on Jessie.
Regards,
Apollon
[1] https://docs.mongodb.org/manual/release-notes/2.6-upgrade/
signature.asc
Description: PGP signature
