for testing
prepped for work on 2.09_01
note about 2.06
Ignore file .timings.json
Add --color option to timings script

Setting the --color option causes the timings script to
color the timings based on whether they were faster or slower than
the previous ack tested.  Right now it's a simple faster/slower
distinction, but in the future we could take advantage of larger
colorsets that more modern terminals provide if we want.
Add --times option to timing script

This option allows a user to run the acks several times over to
try and get a more accurate measurement
Start on ack developer's guide
Updates to the developer guide
Added missing return to Ack::Filter::Is::to_string
Start of log about how to cut a release
note about 2.1 vs 2.10
Add "But I can't contribute" section to DEVELOPERS

This section is intended to educate users on ways they
can help with ack
Add a comment
when shelling out, make sure to at least try to escape some of the payload
mark some failing win32 tests as TODO, since their feature is not implemented yet
mark one failing win32 test as SKIP, since their feature is not implemented yet and the test goes into an endless loop
Fix squash and build process

This addresses issue #23.  It solves the problem by putting ack
at the end of the generated file rather than the beginning.  The
reason I did this is although it was a low priority, it caused
confusing behavior when using module-level variables, and it
could cause untold confusion in prospective contributors.
Start on "source tour" section of DEVELOPERS
Start on "How do I...?" section in DEVELOPERS
Start on Community section in README