Release.markdown

How to work on a Jasmine Release

Development

Jasmine Core Maintainers Only

Follow the instructions in Contribute.markdown during development.

Git Commits

Version

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.

This version is used by both jasmine.js and the jasmine-core Ruby gem.

Update the Github Pages (as needed)

Github pages have to exist in a branch called gh-pages in order for their app to serve them. This repo adds that branch as a submodule under the pages directory. This is a bit of a hack, but it allows us to work with the pages and the source at the same time and with one set of rake tasks.

If you want to submit changes to this repo and aren't a Pivotal Labs employee, you can fork and work in the gh-pages branch. You won't be able to edit the pages in the submodule off of master.

The pages are built with Frank. All the source for these pages live in the pages/pages_source directory.

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
2. Update any comments on the public interfaces
3. rake doc - builds the jsdoc pages
4. Update any links or top-level landing page for the Github Pages
5. rake standalone - builds the standalone distribution ZIP file
6. rake build_pages - builds the Github Pages
7. rake release - tags the repo with the version, builds the jasmine-core gem, pushes the gem to Rubygems.org

There should be a post to Pivotal Labs blog and a tweet to that link.