Hello,

As most of you know Bacula release version 1.40 is nearing -- it was 
originally scheduled for mid-November but delayed due to my vacation and 
several bugs.  

I'm still targeting it before the end of the year, but it looks like one major 
new feature will not be enabled, and that is data encryption.  The code just 
is not stable (it doesn't pass a simple regression test), and it affects the 
Volume data format, and it has known bugs (digest problems), which means that 
if any fixes involve changing the data format (as one does that I found this 
morning), it will create incompatible Bacula Volumes.  This have never 
happened before in the 7 years of Bacula's existence.  

The bottom line is that unless I have a definitive solution (i.e. a bug fix 
rather than a rewrite) to the remaining encryption problems by next Friday, 8 
December, it will most probably not be a Bacula feature until much later (mid 
to late 2007).

One alternative solution is to postpone the release of version 1.40 until late 
March 2007.  Since in all other respects 1.40 is ready to go it would be a 
shame to postpone the release any longer.  Obviously as with all new releases 
there is the possibility of a few bugs particularly in the new features, but 
there should be no show stoppers such as Volume format incompatibility that 
are present in the encryption code.

As always, your comments are welcome.

Best regards,

Kern

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to