version_bumper

Simple. Bump your versions.

What is it for?

Given that we agree upon a version format, maintain a version for your project. The version is kept in a file, in the root of your project, which is a common thing to do.
Especially useful for developers using rake as their build runner in non-ruby projects (don't you?).

Quick start

$ gem install version_bumper

First lets agree that version looks like this: major.minor.revision.build
In your Rakefile require 'version_bumper' and you're done. If you're in rails, gem 'version_bumper' to your Gemfile in addition.

$ rake -T
rake bump:build     # bump build
rake bump:init      # write a blank version
rake bump:major     # bump major
rake bump:minor     # bump minor
rake bump:revision  # bump revision


$ rake bump:init
version: 0.0.0.0
$ rake bump:revision
version: 0.0.1.0
$ rake bump:major
version: 1.0.0.0

You can optionally use bumper_file 'version.txt' in your rake file to switch from the default VERSION file name. Use bumper_version anywhere you need access to the current version in your rake script.

Contributing to version_bumper

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
  • Fork the project
  • Start a feature/bugfix branch
  • Commit and push until you are happy with your contribution
  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Commiters

jondot (Dotan Nahum)
splattael (Peter Suschlik)

Copyright (c) 2011 Dotan Nahum. See LICENSE.txt for further details.