From 33641578e6f7d90be6155ea6dcb262b11a326fea Mon Sep 17 00:00:00 2001 From: slackersoft Date: Fri, 18 Jul 2014 14:27:18 -0700 Subject: [PATCH] update release doc to use github releases --- RELEASE.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 1f311357..6a907f6a 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -20,7 +20,7 @@ The current version lives in the file `/package.json`. This file should be set t This version is used by both `jasmine.js` and the `jasmine-core` Ruby gem. Note that Jasmine should *not* use the "patch" version number. Let downstream projects rev their patch versions as needed, keeping their major and minor version numbers in sync with Jasmine core. - + ### Update the Github Pages (as needed) ___Note: This is going to change right after 2.0___ @@ -41,6 +41,7 @@ When ready to release - specs are all green and the stories are done: 1. Build the standalone distribution with `grunt buildStandaloneDist` 1. Make sure you add the new ZIP file to git + 1. Should we still do this? Given we want to use guthub releases... ### Release the Python egg @@ -56,7 +57,10 @@ When ready to release - specs are all green and the stories are done: ### Finally -1. Visit the [Releases page for Jasmine](https://github.com/pivotal/jasmine/releases), find the tag just pushed. Paste in a link to the correct release notes for this release. The link should reference the blob and tag correctly, and the markdown file for the notes. If it is a pre-release, mark it as such. +1. Visit the [Releases page for Jasmine](https://github.com/pivotal/jasmine/releases), find the tag just pushed. + 1. Paste in a link to the correct release notes for this release. The link should reference the blob and tag correctly, and the markdown file for the notes. + 1. If it is a pre-release, mark it as such. + 1. Attach the standalone zipfile There should be a post to Pivotal Labs blog and a tweet to that link.