Sha256: 8ca37070be63e0750ec60d7a44dcd21c2227a5ef46969acf9dab5c79c91eb333
Contents?: true
Size: 1.46 KB
Versions: 3
Compression:
Stored size: 1.46 KB
Contents
[![Build Status](https://secure.travis-ci.org/cucumber/cucumber.png)](http://travis-ci.org/cucumber/cucumber) The main website is at http://cukes.info/ The documentation is at https://wiki.github.com/cucumber/cucumber/ ## Note on Patches/Pull Requests * Fork the project. * Make your feature addition or bug fix. * Add tests for it. This is important so I don't break it in a future version unintentionally. * Commit, do not mess with Rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull) * Send me a pull request. Bonus points for topic branches. ## Running tests gem install bundler bundle install git submodule update --init --recursive rake ## Release Process Before you even attempt to do a release, make sure you can log into cukes.info and touch a file in /var/www/cucumber/api/ruby (see gem_tasks/yard.rake). You need to be able to do this in order to upload YARD docs as part of the release. * Bump the version number in `lib/cucumber/platform.rb`. * Make sure `History.md` is updated with the upcoming version number, and has entries for all fixes. * No need to add a `History.md` header at this point - this should be done when a new change is made, later. Now release it bundle update rake git commit -m "Release X.Y.Z" rake release ## Copyright Copyright (c) 2008,2009,2010,2011 Aslak Hellesøy and Contributors. See LICENSE for details.
Version data entries
3 entries across 3 versions & 1 rubygems
Version | Path |
---|---|
cucumber-1.1.4 | README.md |
cucumber-1.1.3 | README.md |
cucumber-1.1.2 | README.md |