Improve build/release automation

[richardlawrence]

There are currently too many manual steps involved in a new Cuke4Nuke release. Update gem/Rakefile to fix this.

When building a gem...

• Update version in .NET AssemblyInfo files to match gem version to users know which version of Cuke4Nuke.Framework to reference
• Build .NET assemblies
• Then, build gem

[srinivas1980]

I would like to be able to contribute to this issue
I have experience on using ruby and cucumber with rake and nant builds
If there are any pointers on how to go about this let me know.

[richardlawrence]

I currently do the following steps...

For each change:
Change code
Build code
Run unit tests
Run features
Describe changes in History.txt
Commit changes

To package a release:
Bump version number
Update History.txt with version number and summary
Copy build outputs to gem/dotnet
Copy Cuke4Nuke.Framework.dll to each example lib dir
Generate new gemspec
Build new gem
Commit changes
Push local commits
Tag source with version number
Push tags
Publish gem

I'd love to see some or all of this automated in rake. Some of this already exists in Cuke4Duke; you could use that as an example.

Better yet, I'd love to see an automated process that produces multiple packages for the different .NET versions (e.g. VS2008, VS2010, Mono, etc.)

To get involved, fork the project, make changes, and send a pull request. (Check out the guidelines on the wiki to contribute most effectively: https://github.com/richardlawrence/Cuke4Nuke/wiki/Contributing)

Thanks!