pep
/
blog.bouah.net
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

versioning: update date, fix typos and other minor changes 

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2022-09-12 10:01:20 +02:00
parent 6db187787b
commit 2bd0405b8b
Signed by: pep
GPG Key ID: DEDA74AEECA9D0F2
1 changed files with 29 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

54
content/posts/versioning.md
View File

@ -1,44 +1,48 @@
---
title: "Versioning"
date: 2018-08-07T13:27:43+01:00
date: 2022-09-12T12:00:00Z
draft: true
---
*Today I am grumpy at people's expectation of projects, about versioning and
releases. I am mostly concerned about applications rather than libraries in
this article, but I am sure some of this would apply to libraries as well.*
*I finally took time to setup a forge and some old drafts turned up. I am
publishing one of them today as is even though it's 4 years old
(2018-08-07T13:27:43+01:00). I'm not as grumpy as I was at the time but I
still think this applies.*
Today I am grumpy at people's expectation of a free software project, about
versioning and releases. I am mostly concerned about applications rather than
libraries in this article but I am sure some of this would apply to libraries
as well.
Today we were discussing about versioning and releases in the
[poezio](https://poez.io) chatroom.
Poezio is a console client for [XMPP](https://xmpp.org), a small project,
maintained by a handful of contributors to which I am grateful. I also have a
few contributions myself. The application is far from perfect but what
software is anyway.
Poezio is a console application, a small project maintained by a handful of
contributors to which I am grateful. I also have a few contributions myself.
The application is far from perfect but what software is anyway.
The last release in date (as of writing) for the project is `0.11`, published
on Jan 31, 2017. A bit over 1.5 years ago. Yes, the project is still being
The last release -- as of writing -- for the project is `0.11`, published on
Jan 31, 2017. A bit over 1.5 years ago. Yes, the project is still being
actively maintained, but no release is being made for the moment.
*No*, not every project releases with the same regularity. *No*, not every
project have the same understanding of what a release is. Most projects don't
**No**, not every project releases with the same regularity. **No**, not every
project has the same understanding of what a release is. Most projects don't
have the same constraints.
For some projects, releases are sacred, (so-called __stability__, which am I
still in wait of a definition for), and I am happy for them. Maintained for X
months, even years, to which will only be applied security fixes, or critical
bug fixes, (crashes and the like).
For some projects releases are sacred and I am happy for them. Maintained for
X months or even years to which will only be applied security fixes or
critical bug fixes (crashes and the like).
For others, releases are only checkpoints, a way of saying that features are
being added, bugs are being fixed, also possibly get some PR around it.
For others, releases are only checkpoints. A way of saying that features are
being added, bugs are being fixed, and have people talk about it.
What appears in these releases is actually defined nowhere. It is up to
project maintainers to decide what they want to see in. I could very well make
a release every other commit and be happy with it if I wanted to be silly. I
would still be [semver](https://semver.org) compliant, one of the varion
versioning scheme defined out there.
project maintainers to decide what they want to see in. They could very well
make a release every other commit and be happy with it if they wanted to be
silly. They would still be [semver](https://semver.org) compliant -- one of the
various versioning scheme defined out there.
Nothing also mandates I have to backport bug fixes to the current (or
previous) release, and some projects actually cannot afford such a luxury. All
of this takes time, a really expensive resource.
Nothing also mandates they have to backport bug fixes to the current or
previous releases, and some projects actually cannot afford such a luxury. All
of this takes time and that is a really expensive resource in a project.