From 2b59c33811849d73014d84a0f5a96ea177367c6f Mon Sep 17 00:00:00 2001 From: Martin Oberhuber < martin.oberhuber@windriver.com> Date: Wed, 4 Jul 2007 17:09:39 +0000 Subject: [PATCH] Update build notes for TM 2.0.1 I-builds --- .../template/buildNotes.php | 250 ++---------------- .../org.eclipse.rse.build/template/index.php | 4 +- 2 files changed, 25 insertions(+), 229 deletions(-) diff --git a/releng/org.eclipse.rse.build/template/buildNotes.php b/releng/org.eclipse.rse.build/template/buildNotes.php index 843548599f9..5f819f511d0 100755 --- a/releng/org.eclipse.rse.build/template/buildNotes.php +++ b/releng/org.eclipse.rse.build/template/buildNotes.php @@ -27,31 +27,17 @@ Other components may work with earlier Eclipse versions, but these have not been tested. Platform Runtime is the minimum requirement for core RSE and Terminal. Discovery needs EMF, and the RemoteCDT integration needs CDT. -
  • If you use the dstore server, the protocol version number as well as the - default daemon port were updated. You should use an RSE 2.0 dstore server - with this build.
    • -
  • See also the Official TM 2.0 New and Noteworthy - for a summary of interesting changes since RSE 1.0. -
  • No API changes were made in this build. 9 bugs were resolved: - Use - - + + this query to show the list of bugs fixed since the last milestone, - - TM 2.0RC4 - [build notes].
    • + + TM 2.0 + [build notes].
  • For details on checkins, see the RSE CVS changelog, and the @@ -94,14 +80,12 @@ are the best places for you to get started.
    -

    An important part of the Target Management 2.0 Project Plan -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.

    -

    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 +

    No API changes are allowed in the TM 2.0.1 stream. +Therefore, TM 2.0.1 will be fully upward and backward compatible with TM 2.0, +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 @@ -114,10 +98,11 @@ for future releases. Early migration information can also be found right in the bug reports. Look for those that are tagged [api][breaking].

    + Use - - - this query to show the full list of API changes since RSE 1.0.1. + + + this query to show the full list of API changes proposed for TM 3.0. @@ -339,14 +134,15 @@ Use
    - + Use this query for an up-to-date list of major or critical bugs.

    diff --git a/releng/org.eclipse.rse.build/template/index.php b/releng/org.eclipse.rse.build/template/index.php index 0ff0445437c..3f044708ef6 100755 --- a/releng/org.eclipse.rse.build/template/index.php +++ b/releng/org.eclipse.rse.build/template/index.php @@ -18,12 +18,12 @@ User Agreement.

    - +