X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=bacula%2FReleaseNotes;h=fe281432e7b52a794e99ec775404f98b8e6fbf25;hb=9d6e42d0c0d5378095163e51c0a24b7028a39dc1;hp=f8c3a36342746599b1e446d848ed917eb4db4306;hpb=6b470f755654c9406823eb1f8ec4d7b3682e0248;p=bacula%2Fbacula

diff --git a/bacula/ReleaseNotes b/bacula/ReleaseNotes
index f8c3a36342..fe281432e7 100644
--- a/bacula/ReleaseNotes
+++ b/bacula/ReleaseNotes
@@ -1,40 +1,49 @@
 
-       Release Notes for Bacula 3.0.1
+               Release Notes for Bacula 3.0.2
 
-  Bacula code: Total files = 520 Total lines = 205,459 (*.h *.c *.in)
+  Bacula code: Total files = 1,009 Total lines = 205,726 (Using SLOCCount)
 
-The diff between 2.4.4 and 2.5.x is 208,340 lines, so this release
-represents an enormous effort.
+Note, if you are not already running 3.0.x, read the 3.0.x release notes 
+below.  Important!!!
 
-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. However, any
-release of version 2.5.40 or greater requires a database upgrade.
+Version 3.0.2 is primarily a important bug fix update to version 3.0.1 with
+some enhancements (see below).
+
+Changes since 3.0.1:
 
-Changes since 3.0.0:
 Bug fixes:
-  1276, 1274, 1275, 1272 1246, 1268
+  1029, 1285, 1298, 1303, 1304, 1305, 1306, 1307, 1308, 1309, 1311, 1315
+  1317, 1318, 1323, 1325, 1331, 1333, 1335
 
 Fixed:
-- Check for job_canceled() in fd_plugin code.
-- Update Win32 table creation to have new DB version 11 format
-- Remove illegal Options in Exclude of default Win32/64 bacula-dir.conf
-- Remove "Reposition" message when restoring
-- Updated projects file
-- Tweak version string to display versionid field at the end
-  and keep fields order.
-- Add additional mysql connection debug code submitted by:
-  Chandranshu <chandranshu@gmail.com>
-
-Enhancement:
-- Modify insertion of read Volumes in SD to be done before the
-  drive reservation. This ensures that a Volume to be read will not
-  be reserved for writing. Significant enhancement.
+ - Fix problem with the Postgresql driver that sometime displays <NULL> values
+ - Cleanup old job records when starting the Director
+ - Fix bugs in xattr code
+ - Fix encoding problem with Postgresql
+ - Fix that prevents restore by file selection from using Copy job
+
+Enhancements:
+ - Security enhancement for the File Daemon
+ - New directive to specify source address for outgoing connexions
+ - Show volume availability in autochanger when doing restore.
+   This is project 31 in the projects file.
+ - Add accurate=yes/no option to estimate command
+ - Add --with-hostname, --with-bsrdir, --with-logdir to ./configure
+ - Add a restore menu that contructs a full restore when entering a JobId.
+   This is project 2 in the projects file.
+ - Add new Nagios plugin
+
+Compatibility:
+Like always, both the Director and Storage daemon must be upgraded at
+the same time.
+
+Older 3.0.x and possibly 2.4.x File Daemons are compatible with the 3.0.2
+Director and Storage daemons. It should be no need to upgrade older File
+Daemon.
 
 ============ Documentation improvements needed ==================
 
-Note!!!!! The documentation needs rather extensive modifications in the
+Note!!!!! The 3.0.0+ documentation needs rather extensive modifications in the
 following areas:
 
 1. Missing documentation.
@@ -47,7 +56,21 @@ manpower.  If you are unhappy with this situation as we are, we suggest
 you help by submitting patches to the documentation.  Thanks.
 =====
 
-See below for 3.0.0 release notes...
+================== 3.0.1 Release Notes ========================
+
+Version 3.0.1 is primarily a minor bug fix update to version 3.0.0 with
+one enhancement.
+
+================== 3.0.0 Release Notes ========================
+
+The diff between 2.4.4 and 2.5.x is 208,340 lines, so this release
+represents an enormous effort.
+
+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. However, any
+release of version 2.5.40 or greater requires a database upgrade.
 
 ================== Warning !!!!!! ==========================