diff --git a/rse/doc/org.eclipse.dstore.doc.isv/build.properties b/rse/doc/org.eclipse.dstore.doc.isv/build.properties
index 8788dc44d04..e69e2c016e3 100755
--- a/rse/doc/org.eclipse.dstore.doc.isv/build.properties
+++ b/rse/doc/org.eclipse.dstore.doc.isv/build.properties
@@ -18,5 +18,6 @@ bin.includes = META-INF/,\
toc.xml,\
guide/,\
index/,\
- reference/
+ reference/,\
+ provisional_api.html
customBuildCallbacks = customBuildCallbacks.xml
diff --git a/rse/doc/org.eclipse.dstore.doc.isv/provisional_api.html b/rse/doc/org.eclipse.dstore.doc.isv/provisional_api.html
new file mode 100644
index 00000000000..ea205b0f3f0
--- /dev/null
+++ b/rse/doc/org.eclipse.dstore.doc.isv/provisional_api.html
@@ -0,0 +1,32 @@
+
+
+
+
+
+Remote System Explorer API Status
+
+
+
+
+
+
Remote System Explorer API Status
+
Provisional API
+
+
Although RSE API has been reviewed and proven useful in earlier proprietary
+versions, we want to give the Open Source Communitiy a chance to provide public
+feedback and help further improving the APIs. Therefore,
+
+
As of RSE 1.0, all API is considered provisional.
+
+
This means, that we reserve the right to change any API after RSE 1.0
+in a not backward compatible way. All such API changes will be voted on
+by committers on the
+dsdp-tm-dev developer mailing list, and documented in a migration guide
+for future releases. We expect that with Community Feedback, we'll reach a
+stable, hardened API for RSE 2.0. Please give your feedback on
+Eclipse Bugzilla
+under category DSDP, Product Target Management.
+
+
+
+
\ No newline at end of file
diff --git a/rse/doc/org.eclipse.dstore.doc.isv/toc.html b/rse/doc/org.eclipse.dstore.doc.isv/toc.html
index a410f833cfc..19c48bc709d 100755
--- a/rse/doc/org.eclipse.dstore.doc.isv/toc.html
+++ b/rse/doc/org.eclipse.dstore.doc.isv/toc.html
@@ -1,18 +1,39 @@
-
-
-
-
-
-
-
- RSE DataStore developer information
-
-
-
-
Using the RSE DataStore for Remote Communications
-This section provides information for tool developers who wish to
-add server-side tooling capabilities. Using the RSE DataStore tooling
-communication framework, server-side extensions can be written. The Remote System Explorer can be
-extended to interface the new server-side extensions.
-
+
+
+
+
+
+
+
+ RSE DataStore developer information
+
+
+
+
Using the RSE DataStore for Remote Communications
+
+This section provides information for tool developers who wish to
+add server-side tooling capabilities. Using the RSE DataStore tooling
+communication framework, server-side extensions can be written. The Remote System Explorer can be
+extended to interface the new server-side extensions.
+
+
+
Provisional API
+
+
Although RSE API has been reviewed and proven useful in earlier proprietary
+versions, we want to give the Open Source Communitiy a chance to provide public
+feedback and help further improving the APIs. Therefore,
+
+
As of RSE 1.0, all API is considered provisional.
+
+
This means, that we reserve the right to change any API after RSE 1.0
+in a not backward compatible way. All such API changes will be voted on
+by committers on the
+dsdp-tm-dev developer mailing list, and documented in a migration guide
+for future releases. We expect that with Community Feedback, we'll reach a
+stable, hardened API for RSE 2.0. Please give your feedback on
+Eclipse Bugzilla
+under category DSDP, Product Target Management.
Although RSE API has been reviewed and proven useful in earlier proprietary
+versions, we want to give the Open Source Communitiy a chance to provide public
+feedback and help further improving the APIs. Therefore,
+
+
As of RSE 1.0, all API is considered provisional.
+
+
This means, that we reserve the right to change any API after RSE 1.0
+in a not backward compatible way. All such API changes will be voted on
+by committers on the
+dsdp-tm-dev developer mailing list, and documented in a migration guide
+for future releases. We expect that with Community Feedback, we'll reach a
+stable, hardened API for RSE 2.0. Please give your feedback on
+Eclipse Bugzillaunder
+category DSDP, Product Target Management.
+
+
+
\ No newline at end of file
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/usingAPIs.html b/rse/doc/org.eclipse.rse.doc.isv/guide/usingAPIs.html
index 386ffeb36eb..8999da76ffa 100755
--- a/rse/doc/org.eclipse.rse.doc.isv/guide/usingAPIs.html
+++ b/rse/doc/org.eclipse.rse.doc.isv/guide/usingAPIs.html
@@ -25,7 +25,30 @@ The API set supplied by the RSE can be roughly partitioned into three areas:
This guide will introduce the capabilities of the API, leaving the programming details to the
-reference section.
+reference section.
+
+
Provisional API
+
+
+
+
Although RSE API has been reviewed and proven useful in earlier proprietary
+versions, we want to give the Open Source Communitiy a chance to provide public
+feedback and help further improving the APIs. Therefore,
+
+
As of RSE 1.0, all API is considered provisional.
+
+
This means, that we reserve the right to change any API after RSE 1.0
+in a not backward compatible way. All such API changes will be voted on
+by committers on the
+dsdp-tm-dev developer mailing list, and documented in a migration guide
+for future releases. We expect that with Community Feedback, we'll reach a
+stable, hardened API for RSE 2.0. Please give your feedback on
+Eclipse Bugzilla
+under category DSDP, Product Target Management.
+
\ No newline at end of file
diff --git a/rse/doc/org.eclipse.rse.doc.isv/provisional_api.html b/rse/doc/org.eclipse.rse.doc.isv/provisional_api.html
new file mode 100644
index 00000000000..ea205b0f3f0
--- /dev/null
+++ b/rse/doc/org.eclipse.rse.doc.isv/provisional_api.html
@@ -0,0 +1,32 @@
+
+
+
+
+
+Remote System Explorer API Status
+
+
+
+
+
+
Remote System Explorer API Status
+
Provisional API
+
+
Although RSE API has been reviewed and proven useful in earlier proprietary
+versions, we want to give the Open Source Communitiy a chance to provide public
+feedback and help further improving the APIs. Therefore,
+
+
As of RSE 1.0, all API is considered provisional.
+
+
This means, that we reserve the right to change any API after RSE 1.0
+in a not backward compatible way. All such API changes will be voted on
+by committers on the
+dsdp-tm-dev developer mailing list, and documented in a migration guide
+for future releases. We expect that with Community Feedback, we'll reach a
+stable, hardened API for RSE 2.0. Please give your feedback on
+Eclipse Bugzilla
+under category DSDP, Product Target Management.