which is given to client by the org it consists of testing documents like testplan,testscenarios,testcases,executionreports, scripts.etc...

Release note is given to the customer alongwith the product on the last day.
It contains
*Platforms on which products was tested, not tested

A Release notes is a document from the development team which contains the details of that release that was made to QA for testing. This should normally contain the following details
a) The version label of code under configuration management
b) Features part of this release
c) Features not part of this release
d) New functionalities added/Changes in existing functionalities
e) Known Problems
f) Fixed defects etc.
5. Stick to the input and exit criteria for all testing activities. For example, if the input criteria for a QA release is sanity tested code from development team, ask for sanity test results.
6. Update the test results for the test cases as and when you run them
7. Report the defects found during testing in the tool identified for defect tracking
8. Take the code from the configuration management (as identified in plan) for build and installation.
9. Ensure if code is version controlled for each release.
10. Classify defects (It can be P1, P2, P3, P4 or Critical or High or Medium or Low or anything) in a mutual agreement between the development team so as to aid developers prioritize fixing defects
11. Do a sanity testing as and when the release is made from development team.

Hope that you got what you need...
Shashi