No API changes are allowed in the TM 2.0.x maintenance stream.
Therefore, TM 2.0.x is fully upward and backward compatible with TM 2.0 and TM 2.0.1,
and can be fully exchanged for TM 2.0 in any product based on it.
For the upcoming TM 3.0 release, some API changes will be inevitable.
Although we completed a great deal of API cleanup for TM 2.0, we decided
to still mark all API as provisional since we expect more work to do.
If anyhow possible, we will avoid breaking API changes after TM 2.0, but please
be prepared for future changes, and especially take care of API marked as
@deprecated in the Javadoc.
Such API is prime candidate to be removed in the future. All
API changes will be voted by committers on the
dsdp-tm-dev developer mailing list, and documented in a migration guide
for future releases. Early migration information can also be found right
in the bug reports. Look for those that are tagged [api][breaking].
|