diff --git a/releng/org.eclipse.rse.build/template/buildNotes.php b/releng/org.eclipse.rse.build/template/buildNotes.php index b4bfcb4a070..435568db58d 100755 --- a/releng/org.eclipse.rse.build/template/buildNotes.php +++ b/releng/org.eclipse.rse.build/template/buildNotes.php @@ -26,39 +26,33 @@
  • TM @buildId@ requires Eclipse 3.3M6 or later. Platform Runtime is the minimum requirement for core RSE and Terminal. Discovery needs EMF, and the Remotecdt integration needs CDT.
    • -
  • Added a Telnet Subsystem. It can be activated by selecting the new - system type "Telnet Only (Experimental)". The telnet subsystem is currently - still experimental because of problems when passing invalid credentials, or - opening multiple telnet shells simultaneously. - [178201].
    • -
  • Added ability to show translatable property set names - [188284].
    • -
  • Fixed automatic creation of Mnemonics, added a Policy API to - allow products configure the policy for mnemonic generation - [178768] - [187860].
    • -
  • Persistence of RSE objects is now done in .metadata by default. - This fixes problems with workspace locking. Existing connection definitions - in the old format are still read and understood. The old default behavior - can be restored by a Preference setting. For details, see bug - [187647].
    • -
  • Fixed many problems with externalized Strings relevant for translated - versions of RSE with NL packs.
    • - -
  • At least 8 API changes and 32 bugs were fixed: use - - +
  • At least 13 API changes and 66 bugs were fixed: use + + this query to show the list of bugs fixed since the last milestone, - - TM 2.0M7 - [build notes].
    • + + TM 2.0RC1 + [build notes].
  • For details on checkins, see the RSE CVS changelog, and the @@ -110,7 +104,7 @@ 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 earlierst +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.

    @@ -137,9 +131,33 @@ More information can be found in the associated bugzilla items.