I am supposed to manage the software release process for a product release scheduled this month. Somehow, I couldn't find a good release guide for the different kinds of documentation involved in a product release. The best I could think of at the moment are:
Are there any other documents that should be bundled with a product release? Is there a standard to this?
Anything that is necessary or helpful for the user should be bundled with the product. There isn't really a standard to what should be bundled, but easy to read and concise documentation is always good.
Some examples of user documentation include:
Who asked you to manage the release documentation? Who are you releasing to? What are their expectations re. documention? Has your org ever released in the past (and if so with what documentation)?
What other documentation do you have already (which may or may not be categorized as "release documentation"): for example do you already have software development project management documentation (how to build, bug database, list of requirements, project backlog)? Do you have business/accounting documentation? Do you have marketing literature? A list of customers?
As answered before - it significantly depends on what kind of software you are working on and which practices are considered best in your organization.
Though, here is a release checklist that I used to use when releasing one of my products (not only documentation)
Hope this helps!