How do I upgrade to a new version of ICU? Should I be concerned about API changes, a new Unicode version or a new CLDR version)?
Our goal is for ICU upgrades to go smoothly. Here are some steps you can take to prepare for an upgrade, or to make sure that your usage of ICU is upgrade-friendly. • API: ensure that you are not using draft APIs which may have changed in a future release. See the section on API compatibility (§) in the design chapter . • Unicode: See the release notes for particular versions of Unicode to ensure that your code is not affected by property changes or other specification changes. • CLDR: If your application has test cases which depend on specific translations, these assumptions may become invalid if the translation of an item changes, new support is added, or if a country changes its currency. Try not to depend on specific translations, or be prepared to change test cases. Also, a newer version may support additional translations, currencies, types of calenders • Building/Deploying your Application (ICU4C): ICU4C usually builds with symbol renaming ( See: binary compatibility (§) in the
Related Questions
- If even the tiniest backwards incompatible changes to the public API require a major version bump, won I end up at version 42.0.0 very rapidly?
- If I add or modify some dictionary entries, what will happen to my changes when I upgrade to a new version of Wenlin?
- If I purchase ET GeoWizards for ArcGIS 9.1, do I need to purchase the version for ArcGIS 9.2 when I upgrade?
