holland-coredev team mailing list archive

[Tim Soderstrom <tim@xxxxxxxxxxxxxxxxxxxxx>]

This sounds great Andy! Props to BJ as well and it's great to see some good stuff come out of the CodeJam. Wish I was able to contribute more :) On that note, let me know when the new providers have been merged in and I can write up documentation for them. I'll try to keep an eye on the Github messages as well for that.

On May 20, 2011, at 1:51 PM, Andrew Garner wrote:

> Sorry for all the test failure noise over the past few days.   I
> started including all the packages under plugins/* (adding a few stub
> tests and wiping the dust off many old tests as needed) and had been
> working through that mess. :) This is based off BJ's test_runner.py
> script that came out of the code jam last weekend (thanks BJ!).
> We're now generating pylint (static code analysis) and code coverage
> for everything in the amsterdam branch - not just the core holland
> packages.  At the end of the code jam BJ had the random and sqlite
> plugins being tested as well and now we have basically the entire 1.1
> tree.  This means the pretty pylint/coverage numbers are not so pretty
> now since we're including a lot more than just holland-core :)
> 
> It's well past time to release the 1.1.0a2 release and after I QC the
> current state of the plugins I'll tag that later tonight.   I plan to
> go through a few quick alpha cycles with a basic road map of:
> 
> alpha2 (eta: later tonight)
> 
> - Include all the test and documentation improvements
> - Merged the script and delphini (mysql-cluster) plugins that have
> been sitting around in my tree for a while
> - Merged the transactional options into the mysqldump plugin
> (fine-tuning when holland uses mysqldump --single-transaction)
> 
> alpha3 (eta: ~next friday, may 27th):
> 
> - Merging holland-lvm improvements from my abg branch.  This has
> several nice improvements worth focusing a cycle to:
>    * rsync and other backup methods (holland/lvm is no longer limited
> to just tarball backups)
>    * improved reporting when other processes on the system are
> holding snapshots open
>    * improved sanity checking for mysql configurations when critical
> data files have been placed outside of the LVM mountpoint
>    * a better hierarchical implementation of the lvm plugins with a
> base "vanilla" lvm snapshot plugin that just makes snapshots (useful
> for postgres or other cases where you just want to snapshot a
> filesystem)
>    * snapshot-only plugins (when holland just needs to setup data for
> some other backup software)
>    * cleaner, testable code - we have good tests for holland.lib.lvm
> but the actual plugin code is a bit of a mess in the current
> implementation
> 
> This is pretty much done so I expect to get the tests ironed out and
> code merged in over the next week
> 
> alpha4 (eta: ~ friday, jun 3)
> 
> - I have a feature branch to allow mysqldump to auto-skip broken views
> (and dump those out separately) that I would really like to get tested
> and merged in here.
> - Focus on fleshing out test coverage for mysqldump and trimming down
> pylint warnings further
> 
> Then onwards to beta which holland should be on a pretty solid footing
> for to see a stable release optimistically in late June/early July.
> 
> Again thanks for all the hard work at the code jam - BJ's work in
> particularly massively improved the test procedures in amsterdam.
> 
> ~Andy
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~holland-coredev
> Post to     : holland-coredev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~holland-coredev
> More help   : https://help.launchpad.net/ListHelp
>