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

Go Read a Book

There's a lot of shitty news happening lately, and I've been having trouble holding space for it all.

via flower.codes January 24, 2026

ROSCon Korea 2026 Review

After attending my first ever ROSCon in Singapore 3 months ago, I had a chance to participate in the first ever regional ROSCon in (South) Korea! Physical AI is here I had an interesting discussion with a team lead at ROBOTIS, a major Robotics company , o…

via Junwoo Hwang January 24, 2026

[RIDGELINE] Eras

Ridgeline subscribers — I like “eras.” That is, named chunks of time. Japanese history tends to periodicize based on locus of power. The Tokugawa Shogunate reigned for hundreds of years, and so: Edo, where the power was, becomes the period (a big sweeping o…

via Craig Mod — Writer + Photographer January 24, 2026

Generated by openring