4 ms·
We’ve been using a shared Google Docs folder to manage our app’s release notes. We parse the folder in reverse chronological order, paginate 5 at a time and use
by leesalminen 6y ago
We’ve been using a shared Google Docs folder to manage our app’s release notes. We parse the folder in reverse chronological order, paginate 5 at a time and use their doc to HTML converter API. We then cache in Redis for performance. Works great and keeps the development team away from having to update it. Product/support can edit to their content!
- spondyl 6y agoThat's actually a really cool idea. We currently use a rendered Markdown doc but as a team who can forget and then have to do another commit, this would remove the friction required.
- shrikant 6y agoYou mean your app's release notes go beyond just "- Bug fixes and misc. enhancements"? Good on you! (Sorry for the seemingly drive-by, this really annoys me in Play Store update release notes!)
- leesalminen 6y agoOh yes. We used to be lazy developers and do the bare minimum. We sell a SaaS to the SMB field and the feedback we got was that they wanted to know _exactly_ what we were changing in the app. So now we produce full sentence (or paragraph) explanations for every JIRA card that gets into production for our users, including links to updated documentation, training videos, screenshots, etc.