From 8bb70eb6a0c1124e0d8b316ca0f5ddff4ec49ff3 Mon Sep 17 00:00:00 2001 From: Jan Jambor Date: Tue, 21 May 2024 14:40:05 +0200 Subject: [PATCH] =?UTF-8?q?fix:=20Korrektur=20der=20Aufz=C3=A4hlungszeiche?= =?UTF-8?q?n=20in=20der=20Dokumentation=20"Versioning".?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- versioning.md | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/versioning.md b/versioning.md index 7de4ea4..6cd1235 100644 --- a/versioning.md +++ b/versioning.md @@ -7,15 +7,17 @@ YYYY-MM-[RELEASE_TYPE]-N ``` Components of the version number are as follows: - - `YYYY`, `MM`: Year and month of release. - - `RELEASE_TYPE`: Specifies the development stage: - - `alpha`: Initial testing phase. - - `beta`: Near-complete features, further testing. - - `rc` (release candidate): Stability testing, bug fixes. - - `final`: Production-ready release. - - `N`: Incremental release number for multiple releases within one month. + +- `YYYY`, `MM`: Year and month of release. +- `RELEASE_TYPE`: Specifies the development stage: + - `alpha`: Initial testing phase. + - `beta`: Near-complete features, further testing. + - `rc` (release candidate): Stability testing, bug fixes. + - `final`: Production-ready release. +- `N`: Incremental release number for multiple releases within one month. Guidelines: - - Automated scripts should generate version numbers to avoid errors. - - Ensure tool compatibility with the hybrid version format. - - Maintain detailed changelogs for transparency on progression from alpha to final. + +- Automated scripts should generate version numbers to avoid errors. +- Ensure tool compatibility with the hybrid version format. +- Maintain detailed changelogs for transparency on progression from alpha to final.