streamline release process

[igalic]

• make module: rake tasks invisible by default
• change travis_release to a more speaking name like, puppet_community_release
• after module:bump_commit, puppet_community_release should append -rc to our metada.json version

[rnelson0]

I think I see how the last step works, but can you elaborate on the desired workflow?

If it's what I think, the rake task that travis calls should check for -rc and call it a day if it finds it, rather than wasting time erroring out at the forge (I hope that errors!).

[igalic]

i very much hope that blacksmith's module:bump does the sensible thing and makes 1.2.3-rc into 1.2.4, if not, that's a bug in the semver gem.

[igalic]

all done as per voxpupuli/voxpupuli.github.io#21
we're now trying to figure out if that works.
unfortunately, it appears to require a working ruby :D

[igalic]

after the (two;) successful release(s) of puppet-extlib (voxpupuli/puppet-extlib#45 & voxpupuli/puppet-extlib#43) we should migrate the rake task into this repository. (see also voxpupuli/puppet-blacksmith#25 )

[rnelson0]

Actually, I'd love to have this option for my own modules. Could it be put into a ruby gem and included via Gemfile and spec/spec_helper.rb?

[igalic]

i thought about making it a task of blacksmith, but i'm not sure that's a good idea…

---

making it its own gem is a possibility, but then we're very bound to blacksmith…
also, that check changelog task… would have to be a block/yield.

[rnelson0]

Probably not since it hides some tasks. But as a standalone that requires
blacksmith it could be useful when someone wants to opt in

Rob Nelson
rnelson0@gmail.com

[igalic]

nod thanks for the feedback here, @rnelson0!

[igalic]

i think this is solid by now and can be closed