From 74b200a6323b81ce2d88b5785974f42d951ecc7d Mon Sep 17 00:00:00 2001 From: Yves Hoppe Date: Mon, 4 Jul 2016 23:56:22 +0200 Subject: [PATCH] Updated the contribution / release guide from Phing to JoRobo (#224) --- .github/CONTRIBUTING.md | 17 +++++------------ 1 file changed, 5 insertions(+), 12 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 9e5f665..42a2d39 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -29,19 +29,12 @@ If you find any new bugs, or want to raise any type of support issue, please use ## Release Procedure -This is the procedure and checklist for creating a new package. +This is the procedure and checklist for creating a new package: -* Update the version number in `build.ini`. -* Run `phing set-version`. -* Pun `phing` to make the new package for the version. -* Run `phing tag`. -* Push the commits and tags up to Github. -* Go to the releases page on Github. -* Click on the new tag. - - Click the `Edit Tag` button. - - Fill in the title and description for the release. - - Attach the zip-file for the package to the release. Wait for the file to complete uploading! - - Click the `Publish Release` button. +* Update the version number in `jorobo.ini` +* Modify `jorobo.ini`, add your GitHub token and add ` Release` after `Package` +* Run `robo build` to make the new package and auto-upload and release it on GitHub. +* Go to the releases page on GitHub, review the Changelog and change the status from Pre-Release to Stable. * Create a new `` tag in the `manifest.xml` file. - Change the `` tag to the new version. - Change the `` tag to match the URL of the new release.