Versions and the Puppet Forge

[elyscape]

I'm concerned somewhat by the fact that six versions were released yesterday (2.3.2, 2.3.3, 2.3.4, 2.4.0, 2.4.1, and 2.4.2). It seems like most if not all of those could have been consolidated into a single release. Furthermore, not all of those versions have been pushed to Puppet Forge, crucially including 2.4.0, which is what is listed in the README as the version supporting r10k. I put 2.4.0 in my Puppetfile and received an error when r10k failed to retrieve it from the Forge.

Would it help if someone else were involved in the release process?

[acidprime]

Hmm , well to be clear v2.4.0 in that chart should be v2.4.0+, I understand that could be confusing.

I don't push every git tag as a forge build most days as thats pretty standard practice for things like stdlib for instance.

Most people to be honest don't use the forge functionality in the Puppetfile as it does not offer caching like git does.

I agree those releases could have been consolidated better I was on a bit of roll last night.

[ghoneycutt]

I actually like bumping the versions and releasing a new tag every time you do a merge, though I agree with @elyscape that whenever you do tag a release, it should be released on the forge as people are more likely to find your new releases on the forge.

[igalic]

have i suggested yet to use blacksmith for cutting releases / uploading to the forge?