From 959d9652723f77ad3354b6b64acdd6e66fb57d81 Mon Sep 17 00:00:00 2001 From: JohnnyRevay <65253638+jan-revay@users.noreply.github.com> Date: Sat, 18 Nov 2023 17:29:44 +0100 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 944567142..14111c090 100644 --- a/README.md +++ b/README.md @@ -24,7 +24,7 @@ After you updated the `initPC` or `dotfiles` repo (e.g. adding a package, changi 4. **`devel`** - development and experiments, might be inconsistent or broken regularly. Useful, consistent, and fully functional changes from the branch devel might be merged into the branch testing. 5. **`devel-feature-`** - all feature branches should be branched off and merged to devel. Features and bugfixes of `testing`, `stable` or `LTS` should always go through the `devel` branch first (following the change workflow below). -`LTS`, `stable`, and `testing` branches are expected to be **always in a consistent state** so that they can always be used to init a new machine e.g. VM or a bootable partition. The `devel` branch is expected to be broken from time to time (e.g. when working on larger changes "per partes") and it might not always be possible to init a machine using it. Changes are usually pushed to the `devel` branch directly, very large changes can have an individual feature branch however. +`LTS`, `stable`, and `testing` branches are expected to be _always in a consistent state_ so that they can always be used to init a new machine e.g. VM or a bootable partition. The `devel` branch is expected to be broken from time to time (e.g. when working on larger changes "per partes") and it might not always be possible to init a machine using it. Changes are usually pushed to the `devel` branch directly, very large changes can have an individual feature branch however. ✔️ *Note: By stable I mean free of unpredictable behavior and crashes, not as decribed here: https://medium.com/@gordon.messmer/what-does-stable-mean-4447ac53bac8 (TODO toread)*