Updated NEWS and TODO files in preperation for release.

See the files themselves for more details.

2 files changed, 70 insertions, 1 deletions

diff --git a/NEWS b/NEWS
index bb2e016..88169af 100644
--- a/NEWS
+++ b/NEWS
@@ -1 +1,46 @@
-News goes here
+There have been many changes to pm-utils since the last release of
+0.99.4. 
+
+Major changes include:
+
+* All the scripts that make up pm-utils have been rewritten to conform
+  to POSIX and the Single Unix Specification.  Any remaining bashisms
+  or GNUisms are bugs.  If you encounter a script that is not POSIX 
+  and SuS compliant, please file a bug.
+
+* There have been several changes to the way hooks are detected and
+  invoked. If you have a custom-written hook that breaks upon
+  installation of this package, you may have to perform some minor
+  fixups to make it work again.  All the hooks that are supplied with 
+  pm-utils have been updated to take full advantage of these changes,
+  so use them as examples. For more detailed information, see
+  pm/HOWTO.hooks.
+
+* pm-utils now has a modular sleep backend. There are currently
+  plugins for the default kernel sleep methods, the uswsusp tools
+  (s2ram/s2disk/s2both), and rudimentary support for tuxonice. You can
+  switch between the sleep modules by setting the SLEEP_MODULE
+  environment variable to the desired sleep module.  If you want to
+  write a sleep module, see pm/HOWTO.modules.
+
+* pm-utils has a greatly expanded set of debugging features:
+  - If the environment variable PM_DEBUG is set to true, the
+    pm-suspend.log will contain a full trace of all the actions taken by
+    pm-utils.
+  - The HOOK_BLACKLIST environment variable allows you to disable a
+    hook without having to modify it.
+  - The ADD_PARAMETERS and DROP_PARAMETERS environment variables allow
+    you to modify the parameters passed by calling programs (such as
+    HAL).
+  - More complete logging, including logging the commandline
+    parameters, which hooks ran and did not run (and the reasons why),
+    and logging the status codes of executed hooks.
+
+* pm-utils has pkg-config support.  This makes it much easier for
+  other programs to rely on pm-utils for all their suspend/resume
+  quirk handling needs.
+
+In addition to these major changes, there have been a whole slew of
+minor changes and bugfixes.  Most of the major pm-utils related bugs
+that the distributions have encountered have been fixed in this
+release. Please see the ChangeLog for more details.
diff --git a/TODO b/TODO
new file mode 100644
index 0000000..be87ca1
--- /dev/null
+++ b/TODO
@@ -0,0 +1,24 @@
+* pm-utils has no provision for halting the suspend/resume process if
+  a hook fails. Adding naive support for this is easy, getting it
+  right is less so.
+* There are no provisions for configuring the tuxonice backend.
+  Tuxonice has lots of things that can be tuned, but doing so would
+  end up duplicating alot of the tuxonice project's hibernate script.
+  We should talk to their maintainers about merging common
+  functionality.
+* If a hook needs to handle parameters passed from the command line,
+  it has to do that on its own.  A simple parameter-parsing engine
+  might come in handy.
+* Currently, we really only handle suspend/resume.  The
+  powermanagement system chould use some maintenance. Should we also
+  handle other powermanagement-related tasks?  
+* Beef up the abstraction layer between the hooks and the pm-utils
+  core infrastructure.  We should work on making that API stable
+  enough that...
+* pm-utils to become the default low-level userspace power management handling
+  infrastructure for the majority of Linux (and mabye other
+  unixalikes) distributions.  The core pm-utils infrastructure is
+  already fairly distro-agnostic, leveraging it to be os-agnostic
+  should also be possible.  We should get it to the point that any
+  program that needs something to happen when running a power
+  management task uses our functionality instead of rewriting their own.