wip on readme for release

Rakefile

@@ -1,6 +1,6 @@
 require 'json'
 require 'tilt'
-require 'term/ansi-color'
+require 'term/ansicolor'
 
 Dir["#{File.dirname(__FILE__)}/tasks/**/*.rb"].each do |file|
   require file

Release.markdown

@@ -1,7 +1,25 @@
-## Release
+# How to work on a Jasmine Release
-__Jasmine Core Maintainers Only__
+
+## Development
+___Jasmine Core Maintainers Only___
+
+We attempt to stick to [Semantic Versioning](). Most of the time, development should be against a new minor version - fixing bugs and adding new features that are backwards compatible.
+
+The current version lives in the file `src/version.json`. This file should be set to the version that is _currently_ under development. That is, if version 1.0.0 is the current release then version should be incremented say, to 1.1.0.
+
+Follow the instructions in `Contribute.markdown` during development.
+
+## Release
+
+When ready to release - specs are all green and the stories are done:
+
+1. Update the version in `version.json` to a release candidate - add an `rc` property with a value of 1
+1. Update any comments on the public interfaces 
+1. `rake doc` - builds the `jsdoc` pages
+1. Update any links or top-level landing page for the Github Pages
+1. `rake build_pages` - builds the Github Pages
+1. `rake standalone_safe` - builds the standalone distribution ZIP file
 
-The current version lives in the file `src/version.json`. We attempt to stick to Semantic Versioning
 
 ## The Github Pages
 

lib/jasmine.js

@@ -2471,6 +2471,6 @@ jasmine.version_= {
   "major": 1,
   "minor": 1,
   "build": 0,
-  "revision": 1308288921,
+  "revision": 1308359945,
   "rc": 1
 };

src/version.js

@@ -2,6 +2,6 @@ jasmine.version_= {
   "major": 1,
   "minor": 1,
   "build": 0,
-  "revision": 1308288921,
+  "revision": 1308359945,
   "rc": 1
 };