End User documentation
-What does your target audience need to know (and do) to use your product?
-Keep it brief, possibly as part of the application itself (e.g., the “About” menu).

Technical documentation
-What does a technical support & dev’t team need to work on v2 of the product?
-Latest (updated) specification and design documents (Highlight major changes from previous versions of those documents)
-Application source code (accessed on the web (in a separate static branch of your code repository) or else zipped with correct directory structure)
-Usability testing results (from after the Beta release)
-Latest test plan, including actual test cases
-Automated tests (if any)
-Test coverage is a welcome (and optional) addition.

Up-to-date schedule
-Tasks that have been accomplished (of those that were planned)
-Features (of those initially planned) that are pushed to ver. 2 or abandoned
-How much would each such feature cost (in terms of development & testing effort)?

Release notes
-Known issues with associated severities & priorities
-Incl. a link to the actual bug tracking system’s “tickets”, reflecting the issues