|
|
| Line 72: |
Line 72: |
| 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. |
|
| |
| === 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.
| |
|
| |
|
| == Sugar release cycle== | | == Sugar release cycle== |