Building Trust in Releases*
Releasing an open source project is easy. Push code on Github and (optionally) release the package on PyPI, rubygems, or npm, and distribution packages. How do you build trust into releases so that your users can trust your product? If your product is critical to someone’s infrastructure, trust is even more critical.
How do you gain trust of your community? Well, you have to be publicly accountable and transparent to them. You should mostly solve the problems that your project has set out to do. You should be open to the idea that you get it wrong occasionally and you’re willing to listen.
Release management is not just technical. Sure, there are technical bits to it. But it’s also about empathy and making sure you continue to improve your users trust in you. At the very least your project should continue to work after releases, it should be easy to know what changed, and successive releases out to make it easier to setup your project.
In the recent past, I've co-presented at Linuxcon Europe 2016 and done this particular talk at Pycon Pune 2017 with positive feedback.
Nigel is the Gluster CI architect working out of India.
He loves open source as it enables him to contribute to an ever-growing intellectual pool of knowledge. In the past, he contributed to Mozilla as a Tree Sheriff and when he isn’t working he likes to cook or run long distances. Nobody is sure if he actually ever sleeps. He writes occassionally on his blog and opensource.com.