Prepare next release (1.6.0 ?)

[mcdruid]

I think we need to go through the open PRs in reverse order:

• Update php versions #56 unblocks...
• Add basic test to ensure that tarballs can be created #54 as it would then have a "green board" / clean set of test results.
• Fix return value of _writeBlock #53 could then be unblocked as the new test providing some assurance that it does not cause a regression would be in.

(We should also merge #58 if we're doing #56 - more clean up.)

Then we could prep for a new release that would include #53 + #50 (the latter is already merged).

There wouldn't be any breaking changes that I'm aware of, but dropping support for PHP 5 older than 5.6 might warrant at least a minor version bump, so 1.6.x

[mcdruid]

I have some notes about the (PEAR) release process from @ashnazg but have not done one before.

I'm happy to give that a go if we're in agreement that all of these PRs should be merged and form the next release.

[ashnazg]

@mcdruid , I'm looking over things this morning... ping back quickly if you're available and want to work through these together, me navigating and you driving :D ... if I don't hear anything for a bit, I'll start working through the Issues, PRs, and sequence the merges while watching builds.

[ashnazg]

Release prepped (#59), 1.6.0 tagged, GitHub-released, and PEAR-released.