Best practices for release notes documentation in the Washington DC version

[Sonia Ferenczi]

I am looking for best practices to setup knowledge management for release notes.  Should I have two libraries?  Is there such an option?  We are on the Washington DC version. 

Ideally, there will be a library for release notes for all of our applications.  In the library there would be a knowledge base for the application, then internal to IT vs customer facing.   

Suggestions and examples are appreciated. 

tia   

[Mark Manders · Accepted solution]

Create the release notes library as Knowledge Base. Just add the release notes version based (so new article(s) on the new version) and add a knowledge block for internal to the article(s). That way they have the same information as the client (often functional), but included is the technical/troubleshoot information. You make the blocks only visible for internal use (user criteria). It will help in just having one article. Otherwise you will be doing a lot of copy/pasting. (and if there is customer specific knowledge that is of nu use to internal IT, you can put that in external block(s).

[Sonia Ferenczi]

Thank you Mark