From f3cd70d05e7e8d6d5a238c93cfe34c59e527a72f Mon Sep 17 00:00:00 2001 From: Jorijn van der Graaf Date: Sat, 10 Oct 2026 23:42:56 +0200 Subject: [PATCH] AGENTS.md: the versioning rule, as practised MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 0.3.12 is a fix release and stays in 0.3. The patch number counts releases, and the minor number last moved with emergency calling (f2a4048, 0.3.0). Nothing in the repository said so; §11 now does, so a release's number is not re-decided each time. --- AGENTS.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 4e8dcad..ddce115 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1019,6 +1019,12 @@ only the imsd side of its bus choice. behaviour, in one sentence how it was tested. A version bump is a commit titled `imsd X.Y.Z` that changes only the `Version` constant and has no body. +- **Versioning.** `0.MINOR.PATCH`: the patch number counts releases, fixes + and features alike; the minor number moves when a release changes what + a user can rely on the daemon for (0.3 added emergency calling), not + with the size of a release; the major number stays 0 — what 1.0 would + mark is not decided, and it is not an ABI change (§8.1: the ABI is + frozen). - **No AI attribution trailers.** Commits carry no `Assisted-by:`, `Co-Authored-By:` or similar lines, whoever or whatever drafted them. - **Signed commits.** Every commit is GPG-signed with the repository's