1,285
edits
Changes
Jump to navigation
Jump to search
Line 57:
Line 57: − + + − + − + − +
Development Team/Release (view source)
Revision as of 19:59, 8 September 2017
, 19:59, 8 September 2017→Fructose (base activity) modules
===<abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> (base activity) modules===
===<abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> (base activity) modules===
* Check out the branch of the project repository,
* Check out the branch of the project repository,
* Make a source tarball, which for most activities is done by {{Code|bundlebuilder}} via {{Code|setup.py}} and will place the tarball in the {{Code|dist/}} directory:
* Make the source tarball and bundle, which for most activities is done by {{Code|bundlebuilder}} via {{Code|setup.py}} and will place the result in the {{Code|dist/}} directory:
python setup.py dist_source
python setup.py dist_source
python setup.py dist_xo
ls -l dist/
ls -l dist/
* Create a git tag to reference the release. The tag name should be in the vXXX form (for example v20).
* Create a git tag to reference the release. The tag name should be in the vXXX form (for example v20).
git tag v20
git tag v20
* Test it carefully, to make sure it starts inside Sugar,
* Test it carefully, to make sure it starts inside Sugar,
* Upload it to a stable location. You need a developer account with Sugar Labs to be able to upload there.
* Upload the tarball to a stable location. You need a developer account with Sugar Labs to be able to upload there.
The preferred location for fructose components is:
The preferred location for fructose components is:
shell.sugarlabs.org:/upload/sources/sucrose/fructose/ (module_name)/
shell.sugarlabs.org:/upload/sources/sucrose/fructose/ (module_name)/
which translates to:
which translates to:
http://download.sugarlabs.org/sources/sucrose/fructose/ (module_name)/
http://download.sugarlabs.org/sources/sucrose/fructose/ (module_name)/
* Push the release tag to the project repository,
* Push the release tag to the project repository,
git push --tags
git push --tags
* Send an announce mail to sugar-devel@lists.sugarlabs.org, with [RELEASE] in the subject. The form will be decided by each maintainer but it should at least include a reference to the source code tarball and an high level, user oriented list of changes.
* 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 ===
=== Using the release script ===