THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Choose the latest green build from the branch and from the mater (url template: github.com/apache/ozone/actions?query=BRANCH_NAME)
- Compare the execution time of the two builds
9. possible incompatible changes
...
:
Since Ozone 1.1 Ozone supposed to be backward compatible. Any incompatible changes should be avoided. Experimental new features can be turned off by default with new feature flags. And new scheme changes should be compatible with the (WIP) upgrade framework2.0 introduced a non-rolling upgrade framework to support upgrades and downgrades even when backwards incompatible features are present. Backwards incompatible features should be added to this framework so that they are not used until the Ozone upgrade is finalized, after which downgrading is not possible. Refer to the non-rolling upgrade user guide, design documents, and developer primer for more information.
Client cross compatibility should also be maintained as much as possible, with sensible error messages provided when this is not possible. An old client should be able to talk to the new Ozone instance, and a new client should be able to talk to the old Ozone instance.
10. third party dependencies/licence changes:
...