I'm getting ready to release the next version of our software. In the past when the release is ready to go I will send around an email saying "release xxx is done" and include a basic set of release notes as well as where to find the software. The company (we're small) knows nothing about what happened during testing or what shape the software is in, any outstanding bugs, risks, other than it's passed "the chris bar".
Is a "Final Release Report" a good way to communicate this information? Equally important, is this a good way to say I've signed off on the release but with these caveats? Will this transparency be beneficial?
I don't know exactly what a final release report would look like. Maybe a Google Doc or an email. It will probably describe my testing work, the results and might include a list of open bugs.