So the project I've been working on is now going to be frozen indefinitely. It is possible that if and when the project unfreezes again, it won't be assigned to me or anybody from the current team. Actually, we inherited the project after it had been frozen before, but there was nothing left by the prior team to help us understand even the basic needs of the project, so we wasted a lot of time getting to know the project well. My question is what do you think we should do to help the people after us to best understand the needs of the project, what we have done, why we've done it, etc. I am open to other ideas of why should we leave some tracks to the others that will work on this project also.  Some steps we already have taken:  technical documentation (not full but at least there is some);source-control system history;estimations on which parts of the project need improvement and why we think so;bunch of unit tests.issue tracker with all the tickets we've done (EDIT)What do you think of what we've already prepared and what else can we do? 
Project frozen - what should I leave to the people after me?
project management;software;knowledge transfer
Some more things to considerIs the project directory structure sane?  Have you revised the code comments? Is the commit     log someway presentable?Gerneral purpose overview (as opposed to technical, which you havestarted), Advised reading on the project, project history ( itsdevelopment cycle, previous project managers, list of staff,requirements/feature specification)UML diagrams, class diagrams, work flow diagrams!Reasons the project has been frozen is always nice.Development environment, IDEs that have been used, build tools, these are covered in the technical docs right?I just thought of some of the things I would have liked to see on a project I recently inherited. What you have already provided is a hell of a lot more than what I got. You will receive major karma points for helping the next team out :)