//////////////////////////////////////////////////////////////////////////////
// 13/01/2011 - DIASER development road-map and projected release cycle     //
// Damian Brasher                                                           //
//////////////////////////////////////////////////////////////////////////////

*** NB: Dec 15th 2010 *** ****************************************************
DIASER Business targets have been met this year: 
[white paper, commercial support programme and sales/marketing materials]
Coding milestones have therefore been adjusted due to these priorities.
Please see http://www.interlinux.co.uk for more information.
******************************************************************************

the priority and order may change 
prefix: ! = complete, p = partial completion / functionality, 
* = currently working on 

January - March 2011 (beta 3) - (Note - Feb 25th 11 - Our company has produced a new product and we intend to deploy DIASER as the core of our RMA procedure)
==============================
    main application
    ----------------
    multi-part volume fill option
    transparent regex for volume pre-fix
    --list and --logs; additional redirect output to file switch
    re-order output of --list command
    node migrate adjustments for sudo
    network availability checks and reports
    option to change node role identity
    XMPP(SNMP) interface
    prune archives
    optional delete volumes from source that have been replicated
    mixed non sudo and sudo node install, currently either/or
    (p *security audit) enhancement: restrict uid command execution
    *transparent re-factoring - checks against Perl::Critic
     - create a style sheet including commands to view and navigate code
     - use array's for long parameter lists
    *more and consistent error handling
    tool for filling and auto-replicating retrospective data slots
    locale and translations

    p *diaser_webgui_1
    ---------------
    p request location and name of conf file
    p configuration tool
    --stats pie chart
    --list formatted output
    --logs 
    --retrieve
    *package as dist, rpm and deb

For later versions
==================
    faster data object retrieval / tighter integration with volume creation
    IPv6 
    detailed backup software integration study, docs/code?
    self healing functionality - if transfers failed or were missed
    enhanced archive validation
    adaptive CPU use 
    S3/Google/RackSpace API descriptors for volumes (with price/storage limiter)
    automatic node fail-over i.e. a->c if b is down (using node identity
        change)