Compatibility policy

Compatibility Policy

Backward compatibility

Backward compatibility is always a high priority for Jagger development team. Much effort is put to stay compatible with earlier released versions and support interfaces provided to our customers. Our goal is to keep compatibility for major release versions (f.e. 1.2.3 to 1.2.2), while milestone versions, produced during development iterations, (f.e. 1.2.2-m4 to 1.2.2-m3) can be incompatible.

However we keep our right to introduce incompatible changes and move forward. If minor change is introduced version number will be increased 1.1.X. In case of major changes - we will increase minor number 1.X.1. Major number X.1.1 will be indexed in case of significant change in functionality. In any case changes will be mentioned in release notes.

Example of minor change: change in interface from public interface MetricAggregator to public interface MetricAggregator <C extends Number> that occured between versions 1.2.1 and 1.2.2.

Example of major change: termination of support of some configuration for our instrument

Forward compatibility

While we are trying to keep forward compatibility as well, we don't guaranty it at all. That means f.e. old versions of our Web client will be not able to show metrics data produced by new version of Jagger.