+ It is necessary to run it only once the first time you move to
+ a 1.39.x beta or to 1.40.0. Upgrading the Bacula version
+ thereafter does not require updating the database again.
+ Depending on the size of your database the script make take a
+ bit of time, to run, but in general, it should be very fast.
+
+==== IMPORTANT DVD Volume format changed ====
+- The current Volume format written by 1.39.22 is different from
+ the format written by previous versions. The two formats
+ are not compatible. Thus any DVDs written prior to 1.39.22 will
+ be unreadable by version 1.39.22.
+
+==== IMPORTANT miscellaneous ====
+- The Gnome console program (gconsole) no longer functions as it
+ should. If you have multiple catalogs, you will need to select
+ the catalog (this I will fix). More importantly, in restore
+ mode, the restore tree is no longer shown in the left pane. I
+ suspect this is due to incompatible changes in the GTK+ API,
+ and hence have given up on gnome and gtk+, as this has already
+ happened several times previously. At some point there
+ will be a new GUI console.
+- The bacula-dir.conf directive Accept Any Volume has been
+ removed because it was never implemented. You must delete all
+ occurrence of this directive for the Director to run.
+- The --mandir ./configure option now points to the top level man
+ directory. The man files will be installed under mandir/man8 and
+ mandir/man1 as appropriate.
+- The "Accept Any Volume" directive has been removed. It was never
+ implemented. Bacula will always accept any valid tape that is in
+ the drive for appending.
+- You *should* be able to use 1.38.x FDs with version 1.39.18 Director
+ and SD providing you do not use any of the new features (runscript,
+ data encryption). It seems to work here, but we do not guarantee it.
+- Your Director and SD must be simultaneously upgraded.
+- The restore command no longer uses the MediaType as the primary method
+ of finding a suitable Storage device. Normally it will select the last
+ device used to write a Volume. If no storage device is defined, it
+ will use the old algorithm which selects the first Storage resource
+ with the correct MediaType.
+- The MD5/SHA1 hash codes kept in the database are now kept in a binary
+ format compatible with the rest of the world. If you are running verify
+ jobs, you *must* do an InitCatalog or all files will show an MD5
+ difference. Also, authentication uses the new algorithm by
+ default, but *should* accept connections from older components (FD) using
+ the old non-compatible algorithm. This has been tested, but more
+ more testing is still needed.