Version 0.9.0

NEWS

@@ -1,3 +1,19 @@
+== Version 0.9.0
+
+This release includes some new functionality and a rework of the chain-load
+mechanism.
+
+ * The service specified via the "chain-to" setting will now only be started
+   if the initiating service completes successfully, i.e. if it terminates
+   normally (with an exit code of 0) and only if it is not manually stopped.
+ * New option "--container" (-o) inhibits system management functions (such
+   as machine shutdown/restart) that are normally enabled when dinit runs as
+   process ID 1. A complementary "--system-mgr" (-m) option enables system
+   management (even when not running as PID 1).
+ * Fixed pinned-started services stopping when released by a dependent
+   service, instead of remaining in the started state, and some other bugs
+   related to pinning. Some issues may remain to be fixed in a later release.
+
 == Version 0.8.2
 
 This is a bug-fix release.

README.md

@@ -1,5 +1,5 @@
 # Dinit
-v0.8.2 (development release)
+v0.9.0 (development release)
 
 This is the README for Dinit, the service manager and init system. It is
 intended to provide an overview; For full documentation please check the manual pages. 

TODO

@@ -1,18 +1,11 @@
-For version 0.9.0:
-------------------
-* "chain-to" can result in an unbreakable loop if the chain is circular. Chained services should not be
-  started during shutdown to prevent this (also avoids a race condition where the chained service is left
-  running when everything else has shutdown).
+For version 0.10.0:
+-------------------
 * Check that desired_state is getting set correctly. (Currently we don't decide whether a service
   will restart until it stops...)
-* Add dinit command line option to run as pid 1 but not as system manager (i.e., in a container).
-  Currently dinit can be used as pid 1 in a container but it may try to shut down the system when
-  it terminates. (This results in a harmless warning, but is not ideal).
+* for non-system init, fail to start if the control socket exists
 
-For version 0.10.+:
+For version 0.11.+:
 ------------------
-* for non-system init, fail if the control socket exists, with option to override this and re-
-  create the socket instead (as system init does).
 * report process launch failure reason (stage & errno) via dinitctl.
 * Show "activated" state in "dinitctl list" output
 * Service description sanity checks:

src/version.conf

@@ -1,4 +1,4 @@
 # Included from Makefiles.
-VERSION=0.8.2
-MONTH=June
+VERSION=0.9.0
+MONTH=September
 YEAR=2020