| Description | Responsible | Status/Answer | Go/No Go |
|---|
| Are we Code Complete | Dev Lead | typically Yes or no |
|
| Are all issues / tasks in the project marked as complete? | Program Lead | typically Yes or No, review issue list and obtain statuses on all items. |
|
| What is the test program | Dev/Test Lead | Describe the testing program (Create a page as part of this release for the testing program if needed) |
|
- Does the code build automatically?
- Is the code in Source Control?
- Have we merged to Master?
| Dev Lead | Code needs to be in GitHub and under Continuous Integration. |
|
| Are there any known issues or limitations with the product? | Dev Lead | If yes, describe where the issues are documented |
|
| Are any of the issues potential blockers? | Dev Lead | If needed, review the open issues for the version in question. If issues exist, plan to fix or document. Reschedule the launch if needed. |
|
| How is the release packaged and installed? | Dev Lead | Describe how the release will be delivered to customers, how customers will install the package. (Maybe this needs to be a requirement specified up front.) |
|
| Have we shown the release to the membership? | Program Lead | Pre-release demo of the release should be given to the membership |
|
Have we documented the release? - Are there installation Instructions?
- User Guide?
- Tutorials?
- Technical / API documentation?
| Dev Lead/ Program Lead | Describe the technical documentation that will be delivered as part of the release. |
|
| Link to file issues | Program Manager | How will bugs against the release be tracked. Provide a link to file issues here. Also provide a link to query issues against the release here. |
|