I though it worth explaining the DIASER release cycle very briefly. Software release cycle is open to interpretation. For example; some web applications are in a perpetual beta state.
I chose to use a fairly formal cycle through various stages, this is appropriate for disaster recovery software:
2005:2006 research/design/testing
2007 – prototype
2008 – alpha-development
2009 – alpha
2010 – beta-1
2010 – beta-2 <– currently
2010 Dec – beta-3
2011 Feb – Release candidate
2011 March – Production (Stable)
…
2011 April -> new versions
Currently DIASER is beta-2. beta-3 milestone is planned for December 2010. See here for more details http://en.wikipedia.org/wiki/Software_release_life_cycle
The Current ROADMAP – or burn-down in AGILE speak, projects a production release early 2011. http://diaser.svn.sourceforge.net/viewvc/diaser/ROADMAP_DEV
June – November 2010 (beta 3)
==============================
main application
—————-
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
sponsored addition to community Linux distributions
listing, upload to: http://perlisalive.com http://pause.perl.org
mixed non sudo and sudo node install, currently either/or
security audit and enhancements: restrict uid command execution
re-factoring – checks against Perl::Critic
more and consistent error handling
tool for filling and auto-replicating retrospective data slots
*diaser_webgui_1
————————
request location and name of conf file
configuration tool
–stats pie chart
–list formatted output
–logs
–retrieve
package as dist, rpm and deb
For later versions
=============
detailed backup software integration study, docs/code?
self healing functionality – if transfers failed or were missed
enhanced archive validation
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)
– Damian









