Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
2.0.0
-
centos 5.6 x64 rpm
-
Build
Description
major version upgrades that might break production servers as is in this case of 2.0.0 should be done manually
i see that mongo-* 1.8.3 rpm were renamed to mongo18-* and 2.0 was introduced as mongo-* which resulted in auto upgrade to new version on my servers.
i would advise to release new version as mongo20-, mongo22- and keep old as mongo18-*, no renaming.