Braindump Versions, Release Notes, and the Road Ahead

May 30, 2016 | 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.

latest which refers to the latest commit on master
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.

Give Your Spouse the Gift of a Couple's Email Domain from mtlynch.io
Skip the Next iPhone from Articles on Jose M.
Have smart glasses finally hit an inflection point? from The Torment Nexus
The McPhee method from the jsomers.net blog
Pluralistic: LLMs are slot-machines (16 Aug 2025) from Pluralistic: Daily links from Cory Doctorow
Pluralistic: Bluesky creates the world's weirdest, hardest-to-understand binding arbitration clause (15 Aug 2025) from Pluralistic: Daily links from Cory Doctorow
Just a Little More Context Bro, I Promise, and It’ll Fix Everything from Jim Nielsen’s Blog
The Futzing Fraction from Deciphering Glyph

Articles from blogs I follow around the net

If you’re like me; you like files, you like web technologies like HTML, CSS, and JavaScript, you like markdown, you like kanban, you like pomodoro, and you like apps. If this sounds like you reach out. I’ll be open sourcing something in the coming weeks a…

via Colin Devroe September 3, 2025

Pluralistic: The worst possible antitrust outcome (03 Sep 2025)

Today's links The worst possible antitrust outcome: Hope you like enshittification. Hey look at this: Delights to delectate. Object permanence: Amazon drivers hang phones from trees; DVD Jon v Windows DRM; Chevron's dirty tricks. Upcoming appearan…

via Pluralistic: Daily links from Cory Doctorow September 3, 2025

Give a Problem. Grow a Programmer.

In 2009, I kicked off my senior year in college with a class that ultimately changed the way I thought about my degree—and my future.

via flower.codes September 3, 2025

Generated by openring