Do I need to retest/re-certify my application against a new version of MySQL Cluster?
Ultimately, this is a decision for the application owner and is typically a balance between the time and effort that would be required to retest the application versus the predicted probability and impact of a problem being found if the application is deployed without retesting. The application owner should also consider whether it is necessary to re-do their performance measurements with the new MySQL Cluster version. There are two main reasons why an application could potentially start to fail when ported to a new version of MySQL Cluster: • Intentional functional or API change introduced to MySQL Cluster • Code bug accidentally introduced as part of the release There are three classes of version change for MySQL Cluster: • Major version: Indicated by the X in the X.Y.Z version changing. These versions will typically introduce significant new functionality as well as significant code churn. The probability that new bugs or functional/API changes that are incompatible with your applic
