OpenBSD 7.4
OpenBSD 7.4
OpenBSD 7.4
Open Sourcing IFC SDK for C++ Modules - C++ Team Blog
How to get started hacking NetBSD
cppfront: Autumn update
NetBSD 10.0 timeline and branch status
TypeScript is Surprisingly OK for Compilers
Permanently Deleted
Inside STL: The deque, design - The Old New Thing
Snapless Ubuntu
Inside STL: The pair and the compressed pair - The Old New Thing
Emacs 29.1 Released
WG21, aka C++ Standard Committee, July 2023 Mailing
Six New Security Advisoriers: NetBSD-SA2023-00
There are a few assumptions in here in order for that to work: the known-good version needs to be the latest upstream version (otherwise you might not have the latest security fixes) and users need to be comfortable always using the latest flatpak version. Some users might be more comfortable staying on a known stable version for some time.
Right, and each project will have its own way of handling security issues (particularly when it comes to older versions). Will they point out that versions x - y of their flatpak are affected by a security issue in component z?