Skip to content

Conversation

bdunne
Copy link
Member

@bdunne bdunne commented Sep 7, 2013

No description provided.

jrafanie and others added 11 commits September 7, 2013 12:03
The normal workflow should be:
1) Make your linux_admin code changes.
2) Test and commit these changes.
3) When ready for a new tag...
4) Run rake release
5) This will invoke the update_changelog rake task, it will ask you to:
6) Update LinuxAdmin::VERSION.
7) Verify that the script correctly added the commits since the last tag to the beginning of the CHANGELOG.md.
8) Add the correct version information before these commits.
9) Commit these changes
10) Hit enter and rake release will be run to create the tag, and push the version to rubygems.org.
@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling 3a42b15 on brandondunne:automate_release_process into a2d69f6 on ManageIQ:master.

@bdunne
Copy link
Member Author

bdunne commented Sep 7, 2013

@jrafanie @Fryguy Building on LJ's #26 ... let me know what you think

You can try it yourself by running rake prepare_for_release walk through the prompts and see the commit created. It won't actually release a new version.

rake release with the input should release a new version, so use caution.

Done:

  • If the version file is modified since the last release tag it will use that version, don't prompt user.
  • Always prepend to the changelog then allow time for editing.
  • You can modify changes before confirming and committing.

TODO:

  • Add missing release notes to the changelog? (create history)
  • Create shortcut rake tasks for people who want all of the defaults and don't want to be prompted for anything

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling d98c807 on brandondunne:automate_release_process into a2d69f6 on ManageIQ:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling e361a91 on brandondunne:automate_release_process into a2d69f6 on ManageIQ:master.

@bdunne
Copy link
Member Author

bdunne commented Sep 7, 2013

Not sure if this should be merged here, I think it is a perfect candidate for a git submodule

@cfme-bot
Copy link
Member

Checked commits bdunne@3241888 .. bdunne@e361a91 with rubocop
2 files checked, 16 offenses detected

Rakefile

tasks/release.rake

@jrafanie
Copy link
Member

Closing as stale, we can re-open if this becomes active again.

@jrafanie jrafanie closed this Nov 14, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants