| 18 Nov 2025 |
 raitobezarius | (b) the sysadmin guidance on tmpfs | 16:58:11 |
| raitobezarius | i did mark things that were already in 2.93.1 normally in the body, but the release notes are "raw" | 16:58:31 |
 Winter | but the release notes are "raw"
still kinda not accurate if it's in the 2.94 relnotes bc it was in 2.93...? | 16:59:06 |
| raitobezarius | 2.94 branched off 2.93.0 | 17:00:12 |
| raitobezarius | * 2.94.0 branched off 2.93.0 | 17:00:14 |
| raitobezarius | so effectively, it's a "new" thing in the 2.94 series | 17:00:21 |
| raitobezarius | but i understand what you are trying to say | 17:00:26 |
| raitobezarius | if you have an idea on how to make this better, can you open an issue? | 17:00:34 |
| raitobezarius | but ideally, a solution would take into account this branching model or mesh with the releng process | 17:00:48 |
 leona | e.g. an additional hint "We already released this as a security fix in 2.93.1"? | 17:01:49 |
| leona | sorry don't have the energy today for writing a full issue and so | 17:02:02 |
| raitobezarius | just so i understand well, we are talking about the release notes right? | 17:02:07 |
| raitobezarius | no worries | 17:02:10 |
| raitobezarius | we are not releasing every day thankfully :p | 17:02:16 |
| leona | yes | 17:02:17 |
| leona | like you could just write this sentence in the release notes for the items that were already released | 17:02:42 |
| leona | * like you could just write this sentence in the release notes for the parts that were already released | 17:02:46 |
| raitobezarius | i agree with this | 17:03:07 |
| raitobezarius | the RL were hastily merged unfortunately and we do not have a nice way to update them without point releases | 17:03:25 |
