Dan Horák wrote:
Troy Dawson píše v Po 08. 10. 2012 v 14:48 -0500:
On 10/05/2012 04:43 PM, Troy Dawson wrote:
Hello,
I have updated mongodb from 2.0.7 to 2.2.0.
It is currently going through the normal channels for rawhide and Fedora 18.
10gen has a very good track record for being backwards compatible.
According to their documentation "When upgrading a standalone mongod,
2.2 is a drop-in replacement." and "MongoDB 2.0 data files are
compatible with 2.2-series binaries without any special migration process."
If upgrading replica sets and sharded cluster, you should follow the
procedures from their release notes.
http://docs.mongodb.org/manual/release-notes/2.2/#upgrading
What are people's thoughts on bringing it into Fedora 16, Fedora 17,
EPEL6 and EPEL5?
Troy Dawson
I have had requests for mongodb 2.2.0 for Fedora 17, as well as EPEL 6
and 5. I am going to build for those tomorrow and let things sit in
testing for at least a week (2 weeks for EPEL).
The only concern I have received thus far is whether packages will need
to be rebuilt against the new mongodb 2.2.
From everything I have looked at, the answer is no.
The API's should be backward compatible.
The libraries provided are the same name, there is no increase in number.
you can use the abi-compliance-checker tool to confirm that
or look at the upstream-tracker report for mongodb:
http://upstream-tracker.org/versions/mongodb.html
particularly, the compatibility report between 2.0.7 and 2.2.0 versions
is:
http://upstream-tracker.org/compat_reports/mongodb/2.0.7_to_2.2.0/compat_report.html
--
Andrey Ponomarenko, ROSA Lab.
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
