TODO/NEWS: write down that we intend to remove cgroupsv1 support by EOY 2023

After discussions here:

https://lists.freedesktop.org/archives/systemd-devel/2022-July/thread.html

EOY 2023 is apparently what people can agree with, hence let formalize
this in the TODO list, so we don't forget.

diff --git a/NEWS b/NEWS
index e01ab3e2d330cc61cd7ac81b52f33e170b567273..503777e42c8593b60f05e314d7ad7da9e564739d 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,15 @@
 systemd System and Service Manager
 
+CHANGES WITH 252:
+
+        Announcement of Future Feature Removal
+
+        * Please note that we intend to remove cgroupsv1 support from systemd
+          release after EOY 2023. If you run services that make explicit use of
+          cgroupsv1 features, please implement compatibility with cgroupsv2
+          sooner rather than later, if you haven't done so yet. Most of Linux
+          userspace has been ported over already.
+
 CHANGES WITH 251:
 
         Backwards-incompatible changes:

diff --git a/TODO b/TODO
index 58f67c1feb03671cd860a70b0c22eadbe5293886..51ff28ee711f635a6a41ec626b42f435a1968098 100644 (file)
--- a/TODO
+++ b/TODO
@@ -79,6 +79,11 @@ Janitorial Clean-ups:
 
 Features:
 
+* remove cgrouspv1 support EOY 2023. As per
+  https://lists.freedesktop.org/archives/systemd-devel/2022-July/048120.html
+  and then rework cgroupsv2 support around fds, i.e. keep one fd per active
+  unit around, and always operate on that, instead of cgroup fs paths.
+
 * add small wrapper around qemu that implements sd_notify/AF_VSOCK + machined and
   maybe some other stuff and boots it