ebl update copy doc

[bacula/bacula] / bacula / ReleaseNotes

diff --git a/bacula/ReleaseNotes b/bacula/ReleaseNotes
index d3af69cfb6f3c3851e525f5f9de74da46ca896be..11942fcb84e5bfeb7f383a959b9e7f02c146718f 100644 (file)
--- a/bacula/ReleaseNotes
+++ b/bacula/ReleaseNotes
@@ -1,18 +1,52 @@
 
-          Release Notes for Bacula 2.2.0
-
-  Bacula code: Total files = 438 Total lines = 154,329 (*.h *.c *.in)
-
-The major features are:
-- First cut of bat (Bacula Administration Tool)
-- Red/Black restore in memory tree (500 times faster loading).
-- Much faster insertion of attributes (somewhere around 10 times).
-- The Regex Where code to allow easier relocation of restored files.
-- Socket level heartbeat (untested).
-- posix_fadvise() use in the FD to improve performance.
-- Simpler locking in the SD in the reservation system.
-- Much improved Volume reservation code that should eliminate most
-  conflicts experienced in multiple drive autochangers.
-- Detection of file size/date change during backup if enabled.
-- New Recycle Pool feature.
-- Efficient implementation of very large include/exclude lists.
+       Release Notes for Bacula 2.5.16
+
+  Bacula code: Total files = 517 Total lines = 199,415 (*.h *.c *.in)
+
+This Director and Storage daemon must be upgraded at the same time,
+but they should be compatible with all 2.4.x File daemons, unless you
+use some of the new features that affect the FD.  In other words, you should
+not have to upgrade all your File daemons when you upgrade. There is
+no database upgrade needed from version 2.4.x.  However, the next
+BETA release will require a database upgrade.
+
+==================   Warning !!!!!! ==========================
+This BETA release of Bacula 2.5.x development code uses libtool
+to generate the Bacula libraries as shared objects rather than
+being directly linked in as in prior versions.  This means that
+the Bacula shared objects, must either be in a shared object 
+directory known to the loader or they must be in the directory
+that may be specified on the ./configure line using the
+--libdir option as:
+
+  ./configure --libdir=/full-path/dir
+
+the default /lib. If --libdir is specified, there should be
+no need to modify your loader configuration provided that
+the shared objects are installed in that directory (Bacula
+does this with the make install command). The shared objects 
+that Bacula references are:
+
+libbaccfg.so
+libbacfind.so
+libbacpy.so
+libbac.so
+
+If you have problems with libtool or you wish to use the old 
+way of building static libraries, you can do so by disabling 
+libtool on the configure command line with:
+
+  ./configure --disable-libtool
+==============================================================
+
+This release includes large number of new features and changes.
+It should be more or less compatible with previous xx.conf files
+and File daemons providing that you are not using any of the new
+features.
+
+Please see the New Features chapter of the new manual, which documents
+some but not all the new features (we are still working on it):
+
+http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html
+  
+The ChangeLog has more details.