Skip to content

Latest commit

 

History

History
41 lines (31 loc) · 1.87 KB

releasing.md

File metadata and controls

41 lines (31 loc) · 1.87 KB

Releasing new Ansible version

Before checks

  • Check if Foreman’s required version in register.rb needs to be changed.
  • In case you want to start doing the release in the same PR with another commit, make sure that the version bump in version.rb is in a separate commit.
  • All redmine tickets have correct release version
  • Correct versioning (see Semantic versioning)
X.0.0 - Required Foreman version have been changed
0.X.0 - Major feature have been merged
0.0.X - Small fix

Release process

For following actions you need to have access to rubygems.org and permissions for creating tags in the Github repository.

  • Pull latest master or X.X-stable branch
  • bundle exec rake release
  • Push tag: git push upstream vX.X.X

Foreman Packaging

For setup of Foreman packaging follow instructions here: rpm/develop and deb/develop

RPM

  • Pull latest rpm/develop or rpm/X.X-stable
  • Checkout to the rpm/develop or rpm/X.X-stable and create new branch
  • Bump version to the latest: ./bump_rpm.sh packages/plugins/rubygem-foreman_ansible/
  • For specific version: ./bump_rpm.sh packages/plugins/rubygem-foreman_ansible 7.1.2
  • With git diff verify the changes
  • Push a PR

DEB

  • Pull latest deb/develop or deb/X.X-stable
  • Create new branch
  • Bump version: scripts/update_package.rb -n ruby-foreman-ansible -v X.X.X
  • git commit -am "Updated ruby-foreman-ansible to X.X.X"
  • Push a PR