Release Early, Release Often
Posted Friday, March 31, 2017, at 2:27AM
It’s an old saw, but I was wondering today why some projects don’t cut releases more often. The repo for a project may contain the bug fix you need, but it’s just sitting there on GitHub. I think it often just comes down to the fact that making releases is tedious.
You have to update the version number (perhaps in multiple places), update the change log (hopefully), merge your development branch into your release/master branch, create a tag, clean your dev environment, build a distributable package, upload that package, maybe upload some docs, push some commits, etc.
Doing all that manually isn’t much fun, so…
Write a script to do it for you.
Write it in Python or Bash or as a make target or whatever floats your boat. It’s a one-time cost that pays off big.
You can’t quite automate everything–like writing a (good) change log–but you can automate most of the process.
As an example, I wrote this release script for a project I started
a month and half ago. I’ve already made
26 35 alpha releases because it’s so easy to do. Putting in
an hour or two up front was well worth it.
If you’re feeling lazy, you can use something like zest.releaser (for Python projects). I’ve used it in the past and it’s been the inspiration for all the release scripts I’ve written since.