Development Team/Release: Difference between revisions
| Line 42: | Line 42: | ||
which translates to: | which translates to: | ||
http://download.sugarlabs.org/sources/sucrose/glucose/(module_name)/ | http://download.sugarlabs.org/sources/sucrose/glucose/(module_name)/ | ||
** The preferred location for fructose components is: | |||
** The preferred location for fructose components is: http://shell.sugarlabs.org:/pub/sugarlabs/sources/sucrose/fructose/(module_name)/ which translates to: http://download.sugarlabs.org/sources/sucrose/fructose/(module_name)/ | http://shell.sugarlabs.org:/pub/sugarlabs/sources/sucrose/fructose/(module_name)/ | ||
which translates to: | |||
http://download.sugarlabs.org/sources/sucrose/fructose/(module_name)/ | |||
* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v20 for an activity, v0.81.9 for a Glucose module). | * In git add a tag to reference the release. The tag name should be in the vXXX form (for example v20 for an activity, v0.81.9 for a Glucose module). | ||
* 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. | ||