Tigris object storage has a changelog!
Changelogs build trust: we notify users of any changes to the experience, breaking or not. But there’s a kindness in what doesn’t make it into a changelog, too. For some projects, it makes sense to list every single change. Going to the effort of highlighting what’s important makes it easier to cut to what’s critical.
Most of all, we wanted a format that was easy for us to maintain. A changelog is only as valuable as its updates. Our changelog had to fit into how we already communicate with users. We email all our native signup users monthly with an update on what’s new. And we post about major new features on the blog.
There’s a bit of a trend in changelogs right now. Many of them look like Vercel’s changelog. There’s a focus on features with beautiful demos, but smaller changes to the API are missed. Without going as far as the Linux changelog, how can we make space for important changes that impact the user experience, no matter how small?
We decided to go with a blend of highlighting new features, blog posts, and API changes, providing a curated view of what’s meaningful. More than just code changes, we hope it tells the story of building Tigris storage so you can follow along.
Check it out! And please let us know if it’s helpful (or not).
