Bug 482382 - API Removal Process is incomplete for removal of types
Removes the redundant information for the document and point to the
wiki, so that we avoid maintaining the info several times.
Change-Id: Ia24234ef4bf0866328ea59781ab2e90f7a8e7532
Signed-off-by: Lars Vogel <Lars.Vogel@vogella.com>
diff --git a/bundles/org.eclipse.platform.doc.isv/porting/removals.html b/bundles/org.eclipse.platform.doc.isv/porting/removals.html
index 8bc5b7b..ed05341 100644
--- a/bundles/org.eclipse.platform.doc.isv/porting/removals.html
+++ b/bundles/org.eclipse.platform.doc.isv/porting/removals.html
@@ -11,20 +11,9 @@
<h1>Deprecated API removals</h1>
<p>
- Often there is no sufficiently compelling reason to ever remove deprecated API, so the
- API may remain in place indefinitely after the release in which it was deprecated.
- However, there are situations where continuing to maintain the deprecated API
- creates too high a burden for both API developers and clients: the code bloat of
- keeping old implementations, the added complexity of multiple redundant APIs, etc.
- For this reason the Eclipse project has a
- <a href="http://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy">policy</a>
- to occasionally delete deprecated API after providing two years advance notice to clients.
- This section describes API removals that occurred in this release, and upcoming
- removals in future releases.
-</p>
-<p>
- <b>Note that the policy for removing API types is broken, so some of these plans are not implementable, see
- <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=482382" target="_blank">bug 482382</a></b>.
+ Deprecated API can be marked for deletion.
+ See the <a href="http://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy">policy</a> for the details.
+ This section describes API removals that occurred in past releases, and upcoming removals in future releases.
</p>
<p>
