Daemon: Let daemon actions be numbered from 1

[libucw.git] / ucw / doc / relnotes.txt

diff --git a/ucw/doc/relnotes.txt b/ucw/doc/relnotes.txt
index 7dfc41a3a58cd206b59019132e8f2656713e4143..89d9c2c5bc4df8f7179fd7edd514b1ff77437198 100644 (file)
--- a/ucw/doc/relnotes.txt
+++ b/ucw/doc/relnotes.txt
@@ -1,8 +1,26 @@
 Release notes
 =============
 
-5.0 (work in progress)
-----------------------
+WIP
+---
+
+* The <<conf:,configuration file parser>> has been improved:
+** Multiple instances of the configuration parser are supported.
+** *Incompatible:* As there may be more instances, we can no longer use
+   global variables to control the configuration system. In particular,
+   `cf_need_journal` and `cf_pool` variables have been replaced by
+   functions <<conf:fun_cf_set_journalling,`cf_set_journalling()`>> and
+   <<conf:fun_cf_get_pool,`cf_get_pool()`>>.
+** *Incompatible:* Loading of configuration files has been decoupled from
+   the getopt wrapper, so you might need to include `conf.h` for functions
+   which were previously declared in `getopt.h`.
+** New functions have been added:
+   <<conf:fun_cf_open_group,`cf_open_group()`>>,
+   <<conf:fun_cf_close_group,`cf_close_group()`>>, and
+   <<conf:fun_cf_revert,`cf_revert()`>>.
+
+5.0
+---
 
 * *Incompatible:* The `timestamp_t` type has been decoupled from wall clock time.
   It now specifies the number of milliseconds from an unspecified origin, so that
@@ -61,6 +79,7 @@ Release notes
 * *Incompatible:* Several modules now have their own header files:
 ** `process.h` -- all functions related to processes, previously declared in `lib.h`
 ** `io.h` -- functions related to files from `lib.h` and `lfs.h`
+** `time.h` -- timestamps and interval timers, previously in `lib.h`
 
 * *Incompatible:* Several configuration options were renamed or removed:
 ** `CONFIG_FAKE_ELTPOOL` &rarr; `CONFIG_UCW_FAKE_ELTPOOL`
@@ -77,6 +96,10 @@ Release notes
 * `UCW::CGI` support multiple argument tables and UTF-8 mode. Also, it uses the
   proper HTTP status codes when reporting errors.
 
+* Implementation details of <<fastbuf:,fastbufs>> have changed. The new code checks
+  invariants more carefully, so it is possible that custom fastbuf back-ends which
+  are buggy now fail, although they previously seemed to work.
+
 
 4.0 (2009-04-13)
 ----------------