Release Notes: The key themes of this release are documentation and accessibility. A more comprehensive release includes a working example of a personal cloud storage installation (section 14 of the manual). Also included are a detailed listing of rsync switches used for 'heavy lifting' and general improvements to links. Core documentation has been added, including a White Paper and other elements updated. The spec file is further refined for use in Fedora, or for your own packaging requirements. Special developer tools provide e.g. Perl to extract, list all subroutine names and line number, print line num ranges, etc.
Release Notes: This is the first beta-1 release. The configuration walkthrough has improved input validation. The filling mechanism has been rationalized and is configurable via the command line tools. Its operation has been carefully coded to comply to the design outlined in a flow chart included in the release. All volumes are md5sum checked and dated as they enter DIASER. An emergency lock feature has been implemented as well as a simple archive data retrieval tool with configurable options. All of the above changes have been documented, and new sections added.
Release Notes: This is the first deployable alpha. The storage architecture is stable, is able to take real backup data, is upgradable, and is secure, but is limited to these controls: migration, reporting, manual data retrieval, and some management features. A small bandwidth to space conversion chart was added as a pre-cursor to the calculate_lmb subroutine data added to an updated INSTALL. Data flow through the system has been ok for the past two days and does not need Net::SSH::Perl on nodes.
Release Notes: Enough of the core functionality is present in this release that a move away from alpha-dev to alpha has been made. The ability to choose the number of years of operation has been combined with on-the-fly generation of the core "hyper virtual auto-changer" functionality. (This can be (re)generated quickly and allows comprehensive adjustments to be made at any time after installation.) The two core functionality algorithms based on DIAP are now in place and working together to give trial users and developers full control over operation.