Release 4.2.0

[ghoneycutt]

No description provided.

[ghoneycutt]

Followed https://voxpupuli.org/docs/releasing_version/ for my first release. The process is a bit confusing as https://voxpupuli.org/docs/releasing_version/ created a tag for v4.2.0 and pushed it, though the CHANGELOG is here and waiting for review. From the docs, I expected there to be a release pull request.

[ghoneycutt]

Created voxpupuli/modulesync_config#641 to address the trailing whitespace in CHANGELOG.md.

[alexjfisher]

Oops. The tag has been created on the wrong commit (where the metadata.json wasn't correct). I think the release task should have behaved better and refused to run.
The idea is that this release PR (including version number and changelog) would have been merged and then the release task run on the newly updated master.

[alexjfisher]

Did you use the rake task to generate the changelog? That does some line ending fixup. https://github.com/voxpupuli/puppet-firewalld/blob/master/Rakefile#L72-L79

[alexjfisher]

I think I'll get this release out as 4.2.1 and delete the errant tag. Hope this works for you?

[vox-pupuli-tasks]

Dear @ghoneycutt, thanks for the PR!

This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase?

You can find my sourcecode at voxpupuli/vox-pupuli-tasks

[vox-pupuli-tasks]

Dear @ghoneycutt, thanks for the PR!

This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase?

You can find my sourcecode at voxpupuli/vox-pupuli-tasks

[alexjfisher]

4.2.2 is now released. (4.2.1 failed due to an incorrect travis secret)

[alexjfisher]

@ghoneycutt Sorry it didn't go so smoothly for you. Improvements to the docs are always welcome. They read 'ok' to me, but that's probably only because I've done it enough times.