Release Workflow

Draft - ideas welcome

Howto release a new version

Version number format: x.y.z (no v1.2.3!)

Prepare

• Close (+label) processed pull requests / issues
• Update milestones --> nothing open for the upcoming release
• Travis CI must be "green" on latest build

Release

1. Create new changelog
   • Rakefile update version number in config.future_release
   • Create changelog with bundle exec rake changelog
2. metadata.json update version number
3. Create PR
   • Create new branch vx.y.z
   • commit message: "New release x.y.z"
   • Tag commit with version number x.y.z
   • Push commit to upstream
   • Label PR with no changelog
4. Merge
5. Create release with changelog entries from CHANGELOG.md

Deploy

• Upload release to Puppet Forge
  • Create package with puppet module build
  • Upload via website
  • Should be automated with Travis CI in the future
• On major releases:
  • Inform on Gitter
  • Write blog entry