Changes between Version 15 and Version 16 of DeprecatingFeatures


Ignore:
Timestamp:
Dec 5, 2012 12:14:34 PM (9 years ago)
Author:
arv@chromium.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeprecatingFeatures

    v15 v16  
    2929A more controlled approach to removing a feature is to remove the feature from a single port as an experiment.  In this approach, one port removes the feature (e.g., via an ENABLE macro or a run-time setting) and gathers feedback from its release cycle.  If the port succeeds in removing the feature, we can then remove the feature from the remaining ports with greater confidence that they will also avoid problems.
    3030
    31 This approach as two main benefits:
     31This approach has two main benefits:
    3232
    3333 * The risks associated with removing a feature are concentrated on a single port.  If you're passionate about removing a feature, you might have more luck convincing one port to experiment with removing a feature than convincing all the ports at once.  That port can bear the risks, and the project as a whole can learn about the costs of removing the feature.