Forem: Fakiha Rahman Soha

What are Software Versions?

Fakiha Rahman Soha — Mon, 16 Feb 2026 10:03:41 +0000

I used to think software versions are consecutive numbers which change after every update.

Why does something go from v1.1 to v1.2?
Why suddenly jump to v2.0?
Did the developer just feel dramatic that day?
Then one day, while building a small app, it finally clicked.

The First Release

Imagine you and I build a simple app called TaskNest.
It can create tasks and mark them complete. Nothing fancy.
We launch it proudly as:
v1.0.0
That first “1” feels powerful. It says:
“This is real. This is stable. This is ready.”
The zeros? They just mean nothing extra has happened yet.
This format actually follows a simple idea called Semantic Versioning.

A Bug Appears

The next day, someone reports:
“If I create an empty task, the app crashes.”
Ouch.
We fix it immediately.
No new features. No design changes. Just a repair.
The version becomes:
v1.0.1
Notice what changed? Only the last digit.
That last number is like saying:
“Relax. Nothing new. Just a small fix.”
If we fix another tiny issue?
v1.0.2
Small repairs = small number change.

A Feature Grows

A week later, users ask:
“Can we add deadlines to tasks?”
That’s not a fix. That’s growth.
We add deadlines. Everything still works as before. No one’s workflow breaks.
Now it becomes:
v1.1.0
The middle number increased.
That middle number whispers:
“Something new is here.”
Later, we add categories.
v1.2.0
More features. Still safe. Still compatible.

The Big Decision

Months pass. The app grows.
Then we decide to redesign how tasks are stored internally.
Old saved data won’t work.
The API changes.
Developers using our integration must update their code.
This time, it’s serious.
We release:
v2.0.0
That jump from 1 to 2 isn’t about ego.
It’s about impact.
It’s our way of telling the world:
“Careful. This might break things.”

And That’s It
That’s versioning.
Three numbers.
Three signals.

Last number → small fix
Middle number → new feature
First number → breaking change

It’s not random.
It’s communication.

When you see v2.1.3, you’re not just seeing numbers.
You’re seeing history.
And now, every time I ship something, I don’t ask:
“What number should I pick?”
I ask:
“How much did I change the story?”

What are Software Versions