paraslash 0.3.1

[paraslash.git] / NEWS

diff --git a/NEWS b/NEWS
index 8dd5474dd7aa5b22ced8c51600ca96785bbe6c4d..117ce0c79b625e3a48aedb3c4b79a5bda8a13d4b 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,9 +1,30 @@
 NEWS
 ====
 
 NEWS
 ====
 

-------------------------------------------
-0.3.0 (to be announced) "solar saturation"
-------------------------------------------
+---------------------------------------
+0.3.1 (2008-02-23) "liquid interaction"
+---------------------------------------
+
+A mix of cleanups, bug fixes, improvements, and some new features. No
+significant changes to the new database (osl) code, which is generally
+a good sign.
+
+       - Share some similar/duplicate code between the http and the
+         dccp sender.
+       - Generic access control lists for paraslash senders.
+       - dccp sender: Access control lists, connection limiting and support
+         for the allow,deny,on,off,help sender commands.
+       - The default dccp port changed from 5001 to 8000 (suggested by
+         Gerrit Renker).
+       - para_server starts even if not all public keys could be loaded.
+       - Audiod performance improvements.
+       - fix a bug in the "off" command of the http sender.
+       - fix some fd and memory leaks.
+       - Update to gengetopt-2.22.
+
+-------------------------------------
+0.3.0 (2008-01-12) "solar saturation"
+-------------------------------------

 
 paraslash.0.3.0 -- 'WWDBND --what would databases never do?'.
 
 
 paraslash.0.3.0 -- 'WWDBND --what would databases never do?'.
 


@@ -11,10 +32,10 @@ paraslash.0.3.0 -- 'WWDBND --what would databases never do?'.
 Usually one might expect lots of new features AND a big increase in size
 for a major release like this.
 
 Usually one might expect lots of new features AND a big increase in size
 for a major release like this.
 

-However, this release is smaller than the latest 0.2.x releases. The
-decrease in size is mostly due to the removal of some graphical tools
-(which were only quick hacks anyway). But also the fact that the
-mysql code is gone cuts down the size a bit.
+However, paraslash-0.3.0.tar.bz2 is the smallest paraslash tarball
+ever. The decrease in size is mostly due to the removal of some
+graphical tools (which were only quick hacks anyway). But also the
+fact that the mysql code is gone cuts down the size a bit.

 
 Being independent of mysql comes at a cost: The fact that paraslash
 now contains its own database (the object storage layer, osl) increases
 
 Being independent of mysql comes at a cost: The fact that paraslash
 now contains its own database (the object storage layer, osl) increases