View source for TM/3.3 Release Summary

= Target Management 3.3 (Indigo) Information =

== Executive Summary ==

With moving to the Tools toplevel project, the TCF component has moved to its own project under CDT.
The remaining '''TM Terminal''' and '''Remote System Explorer (RSE)''' components have seen steady improvements as well as community contributions in the 3.3 (Indigo) release.

* RSE 3.3 is mostly a maintenance release (stability, performance, usability) 
* An SCP file subsystem has been added
* the SSH / SFTP file subsystm has been made up to 10x faster
* RSE FTP connection has been made robust and supports IPv6 now through Commons Net 2.2
* Terminal has been made more ANSI compliant

The TM Discovery component has been discontinued in 3.3.

The [http://eclipse.org/indigo/planning/SimultaneousReleaseOverview.php?action=project&projectid=tools.tm Indigo Tracker for TM] has more information about individual items.

The [http://www.eclipse.org/downloads/download.php?file=/tm/presentations/TM_3.3_Release_Review.pdf TM 3.3 Release Review Documentation (PDF, 380K)] (also as [http://www.eclipse.org/downloads/download.php?file=/tm/presentations/TM_3.3_Release_Review.ppt PPT, 540K]) provides a comprehensive overview of the TM 3.3 release.

== Progressive Disclosure of Features ==
A sample plugin showing how to hide RSE contributions to the UI is available from [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.rse/plugins/org.eclipse.rse.ui.capabilities/plugin.xml?root=Tools_Project&view=markup Eclipse CVS].

Essentially, RSE functionality is expected to be driven from the "Remote Systems" Perspective. Opening the RSE Perspective should trigger enablement of RSE UI Contributions - although pretty much all of them are in the RSE Perspective only.

== Builds ==
TM and RSE is using PDE Build with Mapfiles, fully repeatable and documented on [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.rse/releng/org.eclipse.rse.build/README_build.txt?root=Tools_Project&view=markup RSE CVS].

In addition to that, we are using using Athena CBI on [https://hudson.eclipse.org/hudson/job/cbi-tm-3.2-integration/ Eclipse Hudson]. The CBI Build is not quite as tested yet as the Legacy build, but we use it for automated unit tests.

== Unit Tests ==

As of the Indigo release, TM and RSE run a set of 115 unit tests automatically on each Athena Build: Just by clicking the "build" button on the [https://hudson.eclipse.org/hudson/job/cbi-tm-3.2-integration/ Hudson / Athena CBI TM Job], one will get immediate unit test results.

In addition to that, the TM Unittests are available from the TM Project Repository and CVS. Download tm.rse.tests and "Run as" JUnit plugin test. From source code, a lot of tests can be modified to run against different connection types.

Finally, even end users can install the TM Tests plugin from the TM Project Repository, without having JUnit or even JDT installed. Just open the RSE Tests view and run the suite.

== Retention Policy ==

* '''Code in CVS''' is left in there forever.
* '''Formal Releases''' are left as ZIP downloads forever on the [http://archive.eclipse.org/tm/downloads Eclipse Archive Site].
** Milestone Builds are kept until the next formal release on the [http://download.eclipse.org/tm/downloads Main Download Site].
** The TM Indigo Project Repository is expected to be kept forever on http://download.eclipse.org/tm/updates/3.3 .

== Project Metrics ==
Some metrics are available from [http://www.ohloh.net/p/5640/analyses/latest TM at Ohloh].

Bugzilla metrics are in the [http://www.eclipse.org/downloads/download.php?file=/tm/presentations/TM_3.3_Release_Review.pdf TM 3.3 Release Review Documentation (PDF, 380K)].