I am not really sure what you want to achieve here but i can give you some input on how i work with release notes.
If you want to freeze the requirements or content for a release in Confluence you can use the padlock to restrict editing of the page to yourself or a certain group of people.
To create "dynamic" release notes you can create a blank Confluence page named "Release notes product v 1.1" and add filter(s) publishing issues from Jira included in Fix/Version v 1.1" based on issue type i.e bug, Story, Task or other attributes.
Together with diagrams like Created vs Resolved for the release, pie charts and a description of the highlights of the release it normally gets very informative for the PO or business.
You can publish almost everything from Jira in diagrams and filters in Confluence but focus on what is really relevant so you don't overwhelm people with information.
Hey there! New in town? Check out the new Confluence product guides! They are chock-full of helpful tips, tricks, and best practices to get you and your team started. Here’s a quick overview...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events