Mongo 2.2.0 vs. 2.4.6 problem

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-12-20 3:52, David Cheney wrote:
> 
> 
> 
> On Fri, Dec 20, 2013 at 8:17 AM, Nate Finch
> <nate.finch at canonical.com <mailto:nate.finch at canonical.com>>
> wrote:
> 
> I believe our tester bot runs on a machine with 2.2.0, which is
> why my tests weren't able to pass on it. I think we should upgrade
> the bot to 2.4.6, so that it at least matches the images we're
> deploying in the field (and so I can commit my replica set code ;)
> 
> 
> no no, we need to get 2.4.6 into the cloud archive all the way back
> to P, then we can upgrade. Doing it the other way around will only
> make our friends in CTS hate us.
> 

IIRC, we have mongo 2.4.6 in the cloud-archive:tools specifically for
Precise. (And we add that archive when bootstrapping [and add-machine,
but we shouldn't do that]).

I'm not sure about Q and R, but Saucy has 2.4.6 w/ssl directly.

So while I do still prefer having the bot on a 2.2 series (because
that is where we are most likely to break compatibility accidentally),
its possible that we can upgrade to 2.4.6 now.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlKz4PwACgkQJdeBCYSNAAMDSQCdFvY4wj8JaSmVwC/6weW/NL6n
XRoAnRsuUCut9Rqu+d1BA+LDhO9oFOlX
=T22L
-----END PGP SIGNATURE-----