admin/jasmine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update release doc to use github releases

Browse Source
This commit is contained in:
slackersoft
2014-07-18 14:27:18 -07:00
parent a1c109ea17
commit 33641578e6
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
RELEASE.md
View File

@@ -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. 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. 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) ### Update the Github Pages (as needed)
___Note: This is going to change right after 2.0___ ___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. Build the standalone distribution with `grunt buildStandaloneDist`
1. Make sure you add the new ZIP file to git 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 ### Release the Python egg
@@ -56,7 +57,10 @@ When ready to release - specs are all green and the stories are done:
### Finally ### 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. There should be a post to Pivotal Labs blog and a tweet to that link.