Changes between Version 6 and Version 7 of DeprecatingFeatures

Timestamp:

Sep 21, 2012, 3:26:08 PM (12 years ago)

Author:

abarth@webkit.org

Comment:

--

DeprecatingFeatures

@@ -19 +19 @@
 == Cold turkey ==
 
+Perhaps the crudest approach to removing a feature is to simply delete it, cold turkey.  We might use this sort of approach when we're sure we understand the costs of removing a feature.  For example, we [http://trac.webkit.org/changeset/123724 removed the first iteration of the PeerConnection API] cold turkey because we knew that the API was not in wide use and that the working group standardizing PeerConnection had redesigned the API.
+
+Removing a feature cold turkey is also appropriate if the feature is actively causing security or stability problems for WebKit.  For example, we [http://trac.webkit.org/changeset/111361 removed support for magic iframes] cold turkey because they were an ongoing source of security vulnerabilities.  In these cases, however, we should be prepared to bear the compatibility costs of removing the feature.
+
 == A port-specific experiment ==
+
+
 
 == Measure, deprecate, and remove ==