Should the release notes live in a Help Center (e.g. Zendesk) or on a Community platform (e.g. Telligent).
You should probably begin answering a question like this with "It depends..." because there are so many variables that should be considered. So I'll elaborate on our scenario in order to tighten the scope of this question.
So now lets look back at my initial question. We are at a pivotal intersection right now...
What do my fellow Community professionals think?
We use Jira to manage our sprint, we put all notes there and we give access to the business leaders that we work with on a daily basis. Additionally, we use Yammer, and I post bi-weekly releases to our Digital page on yammer for anyone that wants to see what we have done.
The community I manage is mainly a support community, so we post product documentation and help, along with downloads, in our Knowledgebase (currently on a separate platform that is more suitable for larger files and storage) and then do a lot of cross promotion of content from the Community to the KB and vice versa. Within each product group we also have a resources page with links to frequently accessed content, wherever that may reside.
Down the road we are looking to incorporate a federated search in the community so that no matter where the content resides (community, KB, training, main corporate website, etc.) people will be able to find it more easily and in less time.
We host release notes are in our developer documentation on Drupal. Our community has 0 documentaiton on it - our pipeline is too large and complex and Telligent wiki (only viable option for us) was assessed by our devs to not be able to handle the volume and dependencies needed.I'm with Derek_Sage on the federated search, though. This is something our community has been asking for since day 1 into our developer documentation (and product patches, support KB) to seamlessly search and find robust results without ever leaving the community. We tried scoping out federated search though and the only option was Open Search, which we don't want at all so we let it go until we change our documentation platform (BHaG 2018).