For details on checkins, see the
RSE CVS changelog, and the
@@ -89,18 +91,16 @@ are the best places for you to get started.
is to harden the APIs which were provisional by RSE 1.0. Naturally, this requires
API changes, and especially moving lots of classes which we cannot guarantee to
support in the future into internal packages.
-As of TM 2.0 M6, most of this work has been completed, and the list of breaking
-API changes is found below with migration info. But although we had planned for
-API freeze with M6, there are still few more cleanup changes that we would like
-to take the opportunity and bring into TM 2.0. Most of these will be made shortly
-after M6, or they will be introduced in a backward compatible manner.
-At any rate, we will avoid breaking API changes after M7, or the earliest
-possible integration build up to M7. 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 for TM 2.0.
-Use
-this query to show the list of API changes planned or done after M6. All
-such API changes are voted by committers on the
+
The list of breaking API changes is found below with migration info.
+See also the release notes as well as migration docs on the Wiki for
+more information.
+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
@@ -332,14 +332,14 @@ Use