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

Doing less, for her

My daughter will be born soon, and I’m reflecting on what that means for my OpenSource work.

via Carlos Becker February 1, 2026

The Browser’s Little White Lies

So I’m making a thing and I want it to be styled different if the link’s been visited. Rather than build something myself in JavaScript, I figure I’ll just hook into the browser’s mechanism for tracking if a link’s been visited (a sensible approach, if I d…

via Jim Nielsen’s Blog February 1, 2026

$29 million stolen from from Step Finance treasury wallets

The Solana-based defi portfolio tracker Step Finance lost 261,854 SOL (~$28.7 million) when a thief gained access to treasury and fee wallets. It's not yet clear how the attacker was able to steal the funds, although Step Finance…

via Web3 is Going Just Great February 1, 2026

Generated by openring