+== Version 0.6.0:
+
+This release adds a number of minor features:
+
+ * Better behaviour when boot fails. User can choose an action from reboot, resume boot process,
+ start the "recovery" service, or power-off.
+ * New service settings for limiting resources at the process level: "rlimit-nofile",
+ "rlimit-core", "rlimit-data", "rlimit-addrspace". Both hard and soft limits can be set.
+ See dinit-service(5) for details.
+ * New "env-file" setting allows per-setting environment to be specified via a file. The file
+ is re-read each time the service process is started.
+ * Added a "--quiet" option to suppress console output from Dinit.
+ * Dinit when run as a user daemon no longer logs via syslog. Logging to file can still be
+ enabled via the "-l"/"--log-file" option.
+ * Added a "--socket-path"/"-p" option to dinitctl, to specify the socket path for communication
+ with the dinit daemon.
+
+A number of minor bugfixes and other improvements are also implemented. An integration test
+framework has been added with a small number of tests, to complement the existing unit tests.
+
== Version 0.5.2:
This is a bug-fix release for several minor issues which have been found in the preceding
-For version 0.6.0:
-------------------
-* Refuse to start new services during shutdown [DONE].
-* On service failure (all services stop when no restart issued), allow user to
- interrupt/ctrl+alt+del when they are prompted to press enter, to allow halt/rebooting instead of
- re-launching the boot service. [DONE][ even better, you can now choose from several options! ]
-* Basic resource limits setting. [DONE, mostly. OpenBSD compilation issues, others need testing].
-* Per-service environment. [DONE].
-* shares_console processes should not be set as foreground process group [DONE]
-* Process start failure: track where in the launch process we get failure (i.e. we send errno over a pipe,
- we should send a state value as well).
-
For version 0.7.0:
------------------
* dinitctl: Warn when stopping a service would cause a dependent to stop. Require a force flag to proceed.
* dinitctl: implement "restart" command.
* provide a way to check configuration for errors (maybe a dinitctl command)
- - eg. check a service and all dependencies
+ - eg. check a service and all dependencies.
+* report process launch failure reason (stage & errno) via dinitctl.
+* "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 1.0:
----------------
about services we are waiting on (or, do this when prompted via ^C or C-A-D).
* Documentation must be complete (see section below).
* Proper support for socket activation?
-* Be able to boot and shutdown Linux and FreeBSD.
+* Chaining of service process input/output?
+* Be able to boot and shutdown Linux and FreeBSD (or OpenBSD).
For later:
----------