From: Rick Bradley <rick@...>
Date: 2008-10-24T01:31:06+09:00
Subject: Re: flog 1.2.0 Released



On Oct 22, 11:53 pm, Ryan Davis <ryand-r...@zenspider.com> wrote:
> flog version 1.2.0 has been released!

Ryan,
Thanks for your continuing hard work on flog -- it is a great tool.

I wanted to remind you (or anyone interested in the material) that a
fork of flog with a significant test suite and some  refactorings
exists on github here:

  http://github.com/flogic/flame

I note that there still exists no test suite for the main release of
flog and none of the readability, testability, or quality refactorings
from flame were picked up for 1.2.0.

There is also documentation of the characterization and refactoring
process I applied to flog by way of an hour-long presentation at the
Ruby Hoedown this fall.  Video of that presentation can be found
online here (many thanks to confreaks for their continuing good
works):

  http://rubyhoedown2008.confreaks.com/11-rick-bradley-flog-test-new.html

My keynote slides (including all history) for that talk are all on
github, here:

  http://github.com/rick/hoedown-2008/tree/master

There also exists for download a package of snapshots of every commit
in the refactoring process, including commit diffs, commit logs, full
code trees, rcov and flog stats after every commit, and with commit
hashes associated with the flame project commits on the github repo
linked above.  That tarball can be downloaded, for those wishing to
review, study, or audit the refactoring, here:

  http://www.rickbradley.com/misc/flog-snapshot.tar.gz

All of this is free for reuse, mangling, heckling (in the conventional
sense of the word), etc., with no strings attached.

My hope here is that noone need wind up at the point I reached last
spring:  attempting to do work to improve flog and realizing that flog
had no tests, and hence couldn't reliably be developed further by
other than its original author.

Rather than work further without tests I built and have donated a
comprehensive test suite and the necessary refactorings to make the
suite possible and the code readable.

I don't aspire to become a maintainer of flog, much less "that other
guy who maintains the version of flog that has tests", but would
rather see my donated work help the mainstream version of flog in
whatever way is easiest.

Thanks again, and best wishes,
Rick