Changes

===<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===

* Build a source tarball

* Check out the branch of the project repository,

If your activity uses bundlebuilder you can use the dist_source command to generate a source tarball. Note, use a clean checkout of the repository - due to how bundlebuilder works at the moment files you would place in the directory e.g. x.patch would be included in the tarball as well.

* 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:

 

  python setup.py dist_source

  python setup.py dist_source

 

ls -l dist/

The tarball will be generated inside the dist directory.

* Create a git tag to reference the release. The tag name should be in the vXXX form (for example v20).

 

* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v20).

* 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.  

* Test it carefully and make it available in 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)/  

 

* 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.

* 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.