<commit_before>### Announcement Posted By:
<NAME> ( [@meskyanichi](http://twitter.com/#!/meskyanichi) )


Backup 3 - Coming Soon!
=======================

I am currently hard at work developing Backup 3.0. This is a __100% rewrite__ of the gem. There are a bunch of goals I've set for this next big release, a few of which are:

* Great test coverage __(100% TDD)__
* Greatly __reduce__ the amount of __dependencies__ and use better dependencies
* Drop SQL-based backup recording (so no more SQLite nor ActiveRecord ORM)
* Recording will be done using pure YAML (no dependency)
* Write code that's a lot more flexible, extensible, modular and maintainable
* A better DSL for the configuration file
* Try to incorporate as much feedback/good idea's I got from you guys (and at least keeping them in mind while building the base structure)
* Allow users to specify everything they need in a single configuration block
* Allow users to utilize multiple databases, archives, compressors, encryptors and storage locations for a __single__ backup
* Allow the user to specify default configuration for particular properties (S3, CF, DB, etc.)
* __Drop Ruby on Rails support__ (This is a pain to maintain and isn't worth supporting, Backup is better without it using the CLI)
* A better Command Line Utility/Interface
* Better defaults, for example no more `/opt/backup` but `$HOME/backup` to avoid permission and other issues for non-root users
* The freedom (through CLI) to specify the location of the configuration file on the filesystem, as well as the location of where the dumped .yml files should be stored and loaded

These are a few of the goals I've set for the next release. Feel free the view the source. I probably won't release the initial version with __every__ feature that Backup 2 has when it first comes out, but it'll have plenty of features to start off with. Also, it'll be __a lot__ easier to maintain it and improve it now that it has good test coverage, and is more modular and extensible. So expect a lot more to come in Backup 3 in the future! I am really excited about this one.


Backup 3 - ETA
==============

There is no ETA yet, but I hope to push the initial version out before __March - 2011__. Then we take it from there. ;)<commit_msg>Noted that Backup 3 is tested against Ruby 1.8.7 and Ruby 1.9.2<commit_after>### Announcement Posted By:
<NAME> ( [@meskyanichi](http://twitter.com/#!/meskyanichi) )


Backup 3 - Coming Soon!
=======================

I am currently hard at work developing Backup 3.0. This is a __100% rewrite__ of the gem. There are a bunch of goals I've set for this next big release, a few of which are:

* Great test coverage __(100% TDD)__
* Tested against __Ruby 1.8.7__ and __Ruby 1.9.2__
* Greatly __reduce__ the amount of __dependencies__ and use better dependencies
* Drop SQL-based backup recording (so no more SQLite nor ActiveRecord ORM)
* Recording will be done using pure YAML (no dependency)
* Write code that's a lot more flexible, extensible, modular and maintainable
* A better DSL for the configuration file
* Try to incorporate as much feedback/good idea's I got from you guys (and at least keeping them in mind while building the base structure)
* Allow users to specify everything they need in a single configuration block
* Allow users to utilize multiple databases, archives, compressors, encryptors and storage locations for a __single__ backup
* Allow the user to specify default configuration for particular properties (S3, CF, DB, etc.)
* __Drop Ruby on Rails support__ (This is a pain to maintain and isn't worth supporting, Backup is better without it using the CLI)
* A better Command Line Utility/Interface
* Better defaults, for example no more `/opt/backup` but `$HOME/backup` to avoid permission and other issues for non-root users
* The freedom (through CLI) to specify the location of the configuration file on the filesystem, as well as the location of where the dumped .yml files should be stored and loaded

These are a few of the goals I've set for the next release. Feel free the view the source. I probably won't release the initial version with __every__ feature that Backup 2 has when it first comes out, but it'll have plenty of features to start off with. Also, it'll be __a lot__ easier to maintain it and improve it now that it has good test coverage, and is more modular and extensible. So expect a lot more to come in Backup 3 in the future! I am really excited about this one.


Backup 3 - ETA
==============

There is no ETA yet, but I hope to push the initial version out before __March - 2011__. Then we take it from there. ;)
{'fraction_non_alphanumeric': 0.06545690213869086, 'fraction_numerical': 0.010153380859796932, 'mean_word_length': 4.383720930232558, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2691315', 'n_tokens_mistral': 1243, 'n_tokens_neox': 1145, 'n_words': 738}