Release notes are made to be socialized with your community. We create them to provide transparency between ourselves and the people using our products and services. That’s why we added a new Twitter integration :)!
Hundreds of teams are already posting their release updates to Twitter, where their community shares, comments, and congregates around the changes. Some companies like GitHub and Heroku have dedicated accounts explicitly for posting changelogs.
These are exciting trends, and we’re happy we’re able to help our customers:
For this integration, we talked with teams already using twitter as a medium for sharing their release notes and reviewed how hundreds of notes had been shared. You can check out the Twitter list we made tracking just a few of the teams we found using Twitter to publish their releases. We also wrote up a few blog posts on our design choices and technical implementation.
With this feature, we continue our effort to bring transparency to our users by sharing the feature announcement and documenting the solution. We are attempting to build additional trust and organic traffic by developing content that helps our users and the broader DevOps community develop their integrations if they need specialized solutions or choose our off the shelf implementation. We are attempting to do a better job of expressing the reasoning for adding the integration and why we configured it the way we did.
It’s been exciting seeing various techniques people are using to build, maintain, and learn from their communities. We’re trying to understand what’s working for others and adopt some of these practices. If you have a social network that you’ve found success in engaging your community, hit us up, we’d love to hear about it!