permit releasing from multiple branches
Merge pull request #1 from karenetheridge/topic/multiple_correct_branches

permit releasing from multiple branches
make Pod::Coverage happy
v0.004
update role ABSTRACT

closes #3
Pull over code from Git::NextVersion that we depend on

This was dropped from the latest releases, and unfortunately, we depend on it.
I'm pulling it in here until a more permanent solution can be found.
....aaand tidy it up.
don't use /dev/null -- closes #4

As it works everywhere but Windows.  Which is still in use, apparently :)
root out more platform-specific code (closes #5)

In this case, relying on mkdir being both present and behaving in a unixy way.
update changelog format
add LICENSE stub
v0.005

	* make our test suite usable on !unix platforms (github #4, #5)
	* Fix breakage introduced by the git NextVersion plugin in  1.122770 by
	  pulling over the removed code and integrating it here.  This is expected
	  to be a temporary measure as we figure out a more permanent (and
	  hopefully cooperative) solution.
Add MergeConflicts - detects common merge conflict markers

Sometimes, you might accidentally add files that have conflict
markers in them without realizing it. This checks each file as
it is added to the dist for common merge conflict markers, and
aborts if they're found.

No tests for this plugin yet.

Fixes GH #6: Feature request: check for merge conflict markers
Merge pull request #7 from doherty/merge-conflict-markers

Add MergeConflicts - detects common merge conflict markers
mark 'git' as a requirement (closes #8)

This doesn't seem to be a problem in use so much as with automated testing.
And, hey, we need it anyways :)
add contributors pod section
make test-eol happy
v0.006

	* Add plugin to check for common merge mishaps [Mike Doherty]
	* Add explicit dependency on the git executable
update travis-ci config
autoadd