> To migrate their first customers without dislocation, they had to hold off on changing the default behavior for longer than they wanted to. This does seem li

> To migrate their first customers without dislocation, they had to hold off on changing the default behavior for longer than they wanted to. This does seem like a sticky situation, but a potential solution springs to mind. Maybe there's a reason this would have been infeasible, but why not introduce a "MongoDB Legacy" product line which would be a fork with unsafe defaults, secondary to the main product/branch with safer defaults? That way the old customers would have a clear upgrade path every release, just like the customers on the safe product, at the small expense of 10gen having to cut 2 releases each time and mind the diffs around options and defaults. Maybe this would have been more expedient than waiting until version 2.6 of MongoDB?