I’ve rebuilt my website! This post isn’t likely to be interesting unless you’re into static site generators or navel-gazing. It’s also not too long, as I’m omitting almost all the gory details.
I’ve been horrid about blogging lately, but didn’t want 2015 to pass with exactly zero posts. First is an open source review/update (the good & the bad), with some more personal topics afterwards. If you’re the skimming type, I bolded the important bits.
Some quick thoughts based on recent Twitter conversations about Python version support in OSS projects, presented in (ironically, given the topic) lazy bullet list format.
A bunch of notes about Paramiko, Fabric and Invoke, such as their websites, their Python 3 support, and more! With copious exclamation points!
Most open source projects store documentation in the source repo itself. This is easy to do, allows the doc builder to reference in-code documentation (like Python docstrings), makes contributions from others simpler, etc.
However, it doesn’t always play nice with “meta” information such as how to contribute, project roadmap, and so forth.
Life has continued to conspire against me, but this particular Friday I successfully wrested some time from other responsibilities and put out a couple of releases.
Changelogs are a frequently overlooked aspect of software release management. I’m going to outline the different approaches to keeping them, and describe a dumb yak shave I undertook to improve the situation for my own projects.
In my previous blog post I mentioned that I intend to begin a regimen of smaller, more frequent releases in my open source projects. Afterwards, I started thinking more about what this meant and how software release schedules work in general. This is the result.
Deciding when to release software can be difficult. Releasing after every patch or merge is typically too much, though some argue otherwise: it depends how you define “often” in “release early, release often”.
The other options are “whenever you feel like it” and “have a specific schedule”.
Until now I’ve always gone with that middle option, waiting until a large-enough set of changes had piled up to merit a new release.