1,286
edits
Changes
Jump to navigation
Jump to search
Line 72:
Line 72: − − === Using the release script === − For both, fructose and glucose components you can use the release script in [https://github.com/sugarlabs/sugar-tools sugar-tools] to do the above tasks in one go. − − You can check out the available commands (Note, the script does try to release the software of the directory you are currently in): − − ./release --help − − ==== For sucrose activities ==== − − ===== Before release ===== − − Be sure to have the same state as origin/master, git pull, git log, gitstatus, git reset --hard origin/master − − ===== Release ===== − − cd into the activity directory, run the sugar-tools 'release' script from there − − ~/prog/sugar-tools/release − − If you want to be sure about the version you can pass the version you want it to be to the script: − − ~/prog/sugar-tools/release -v 0.96.5 − − Requirements: − − * has to be done in a sugar shell − * user needs ssh access to sugarlabs.org − * user needs write access to the upload directory: http://download.sugarlabs.org/sources/sucrose/fructose/ − − ===== Upload the .xo file to ASLO ===== − − Tarball is uploaded but you're not done yet, you need to upload the .xo file to ASLO manually.
Development Team/Release (view source)
Revision as of 15:18, 2 November 2017
, 15:18, 2 November 2017remove sugar-tools release script, as it has not been maintained, and was not used for the 0.111 and 0.112 release, a new maintainer for sugar-tools is welcome
git push --tags
git push --tags
* Upload the bundle to activities.sugarlabs.org, with a high level, user oriented list of changes, which will cause a release mail to be sent to sugar-devel@lists.sugarlabs.org.
* Upload the bundle to activities.sugarlabs.org, with a high level, user oriented list of changes, which will cause a release mail to be sent to sugar-devel@lists.sugarlabs.org.
== Sugar release cycle==
== Sugar release cycle==