Entrance criteria

When a Feature is no longer used and under active support, the Chair of the relevant group shall ensure that:

  • All sub-features should no longer be capable of being activated
  • The Feature Design document’s “current status” has been updated to Feature Archive
  • The TSC is notified about the Feature archival both in the next TSC meeting and on the TSC mailing list
  • The Documentation WG has been consulted on documentation changes

Details

Every effort shall be made to ensure that documented Features that no longer receive support are marked as deprecated, superseded, or archived.  The intent is to keep the information about prior functionality as long as practical.  Images, packages, tests, and other supporting tooling and assets may not be persisted for Historical Features, but the source code may be preserved through GitHub repository versioning.


  • No labels

2 Comments

  1. David Booz

    I'm not sure we need this stage. I think we should remove it. However, this does bring up a question of deprecation of features. It is not uncommon for a new feature to deprecate another. I suspect we need to articulate a deprecation policy, and then weave that into stages 1 2 and 3 as appropriate.

  2. Joe Pearson

    Sounds good, David Booz.  What is the best venue to discuss and flesh out the deprecation policy?