Braindump Versions, Release Notes, and the Road Ahead

| python | programming | projects |

I have been playing with a couple different methods of versioning and release notes with Braindump. I used to do all release notes in GitHub. GitHub “Releases” are nothing more than git tags with some additional meta-data and after talking to eric one day I agree that locking myself into GitHub specific tags is not the best idea. Then I started to add release notes on my blog and just link to it from the GitHub tag, this worked ok but you may have noticed that I blogged about version 0.3.0 yesterday and then released versions 0.3.1, 0.3.2, 0.3.3, and 0.3.4 today. I think I finally came up with a solution that makes the most sense to me.

Braindump is using semver, so the scheme is MAJOR.MINOR.PATCH. So going forward, I will create release notes only for MAJOR and MINOR versions.

With the new Docker deployments I am creating two types of containers.

  1. latest which refers to the latest commit on master
  2. stable which refers to the latest git tag
I also have created some milestones and put every current issue into a milestone. Patch versions are now milestones and they will come and go quickly. Major and Minor versions are going to be more long running milestones. The Ice Box is where dreams to go ~die~ come true some day.

Braindump.pw will always be running the latest patch version, or stable. I hope this new methodology will provide some better structure and clarity for this project.

Thank you for reading! Share your thoughts with me on bluesky, mastodon, or via email.

Check out some more stuff to read down below.

Most popular posts this month

Recent Favorite Blog Posts

This is a collection of the last 8 posts that I bookmarked.

Articles from blogs I follow around the net

Sharing group_var variables across Ansible inventories

The problem Some time ago I worked with a customer that used Ansible to deploy a multitude of applications across their individual TAP1 environments. Unfortunately the Ansible inventory was setup in such a way that group_vars variables for a specific applic…

via Louwrentius December 20, 2025

Thoughts on MCP

I was listening to a recent Vergecast episode the other day, and in there, there was a whole segment about MCP servers and AI-powered shopping. I’ll be honest, I’ve never been more confused about something tech-related. The more I read and listen …

via Manuel Moreale — Everything Feed December 20, 2025

2025 LLM Year in Review

2025 Year in Review of LLM paradigm changes

via karpathy December 19, 2025

Generated by openring