保留旧代码以供参考的惯例是什么？(What is the convention for keeping old code for reference?)

 我有一个相当新的小团队项目和一个新团队，我们尝试了一些不同的方法，并在设计中进行了一些重要的迭代。 
 
 我们有一些不应该使用的类和一些具有ClassStuff和ClassStuffImproved等混乱的类。 我们有SVN，但我认为没有把所有的垃圾拿到手上并且让人们在历史上手动挖掘是有效的。 有些事情可能需要重新正确实施，之前的不良实施将提供参考。 但是我想打破任何依赖于垃圾的东西。 即使这些垃圾文件被破坏，我也希望项目能够构建。 
 
 有文件夹约定吗？ 我应该把所有的nuked内容都放在一个文本文件中，所以当有人想知道一个课程在哪里时，它至少可以轻松搜索到吗？ 
 
 这里的典型惯例是什么？ 

I have a fairly new small team project with a new team and we have tried a few different approaches and had a few significant iterations in design.
 
We have some classes laying around that should not be used and a few classes that have such messes as ClassStuff and ClassStuffImproved. We have SVN but I don't think nuking all the junk and making people dig manually in the history is productive. Some things may need to be re implemented properly and the previous poor implementation would provide a reference. I do however want to break anything that depends on junk. I also want the project to build even if these junk files are broken. 
 
Is there a folder convention? Should i put all nuked content in a textfile so at least its easily searchable when someone wonders where a class went?
 
What is the typical convention here?

原文：https://stackoverflow.com/questions/21121841