Description Martin Oberhuber 2007-05-09 08:23:12 EDT

As discussed in the Committer Meeting on
  http://wiki.eclipse.org/index.php/DSDP/TM/Committer_Phone_Meeting_8-May-2007
we do not consider the Terminal API finished for the TM 2.0 release.

We should therefore mark the Terminal API as provisional. According to 
  http://wiki.eclipse.org/index.php/Provisional_API_Guidelines
Eclipse provisional API guidelines say:
  * Provisional APIs that are not intended to become real API in time for the
    release should be in an internal package.
  * If provisional API is in an internal package, it should kept in a separate
    package from code that is never intended to become API. The
    "internal.provisional" naming convention can be used, but is not required
  * If the API is particularly volatile, experimental, or at risk of removal,
    a further comment in the javadoc can be used to clarify the state of the
    API: <strong>EXPERIMENTAL</strong>

Currently, there is only one API package in org.eclipse.tm.terminal. According
to the guidelines mentioned above, this package should be refactored to

org.eclipse.tm.internal.terminal.provisional        or
org.eclipse.tm.internal.terminal.api                or
org.eclipse.tm.internal.terminal.provisional.api    or

and the Javadoc of those interfaces and classes that we consider "more at risk than others" should get the <strong>EXPERIMENTAL</strong> tag as suggested by the Wiki page mentioned.