Release Report Template - ©
Release ID: / Release Name: / Customer: / Project Manager:Start Date Planned:
DD-MM-YYYY / Actual Start Date:
DD-MM-YYYY / End Date Planned:
DD-MM-YYYY / Actual End Date:
DD-MM-YYYY
Sample Release Report Template
(Byhttp//:
- Scope
<Brief the scope of the project and the build released for testing.>
- References
<List out the reference documents for the release>
- Release Description
This release is a controlled release of <Project Name> and contains following features and functionalities.
The features marked in * are new in this release.
- Module 1
1.1 Feature 1
1.1.1 Functionality 1
1.1.2 Functionality 2
1.2 Feature 2
1.2.1 Functionality 1
1.2.2 Functionality 2
1.2.3 Functionality 3*
- Module 3
2.1 Feature 1
2.1.1 Functionality 1
2.1.2 Functionality 2
1.2 Feature 2
2.2.1 Functionality 1
2.2.2 Functionality 2
2.2.3 Functionality 3
- Module 3*
3.1 Feature 1*
3.1.1 Functionality 1*
3.1.2 Functionality 2*
The following features are not been implemented in this release.
- Module 1
1.1 Feature 1
1.1.1 Functionality 1
- Configuration Management
We are using<Configuration Tool> as configuration management tool. The build is available in the following path.
Internal Link: <internal link for the released build>
External Link: <external link for the released build>
- Installation Instructions and Steps
Give the detailed information for the installation of the build to QA/Testing team.
- Issues / Bugs Fixed
The status of the bugs is updated in <Bug tracking tool>.
- Issues / Bugs To Be Fixed
Sl.No / Bug ID / Bug / Issue Description / Remarks (If any)
1.
2.
- Deliverables
Sl.No / Deliverable / Medium / Status / Remarks
1.
2.
3.
- Known Bugs / Issues
Sl.No. / Bug / Issue Description / Test Case ID / Schedule to Fix / Remarks (If any)
1.
2.
3.
- Release Check List
Sl.No / Description / Y / N
1. / Have all the files been checked in <configuration tool>?
2. / Has the label been put on the proper folder in <configuration tool>as per internal standards?
3. / Is the release identifiable as 'external' / 'internal' release in <configuration tool>?
4. / In the comments, has the version been mentioned in <configuration tool>?
5. / In the comments, has a short description been mentioned in <configuration tool>?
6. / Code has been reviewed and code review issues are logged in <bug tracking tool>?
7. / Code review checklist has been updated and available in <configuration tool>?
8. / Unit test document has been prepared and reviewed?
9. / Unit test cases executed and the results updated for the status?
10. / Updated unit test case document is available in <configuration tool>?
11. / All the <bug tracking tool> issues for this released has been resolved/closed?
12. / All the work package tasks completed and updated in <configuration tool>?
13. / Is Smoke testing done and passed?