Development Team/Release: Difference between revisions

Line 37:

More in detail:

* Build a source tarball, 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 glucose modules is:

=== Glucose ===

shell.sugarlabs.org:/~~pub/sugarlabs~~/sources/sucrose/glucose/(module_name)/

* Build a source tarball

make distcheck

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

* 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 glucose modules is:

shell.sugarlabs.org:/upload/sources/sucrose/glucose/(module_name)/

which translates to:

http://download.sugarlabs.org/sources/sucrose/glucose/(module_name)/

~~The preferred location for fructose components is:~~

~~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).

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

~~Note: You~~ can use the ~~release script in [http://git~~.~~sugarlabs.org/projects/sugar~~-~~tools sugar-tools]~~ to do the ~~above tasks~~ in ~~one go~~.

=== Fructose ===

* Build a source tarball

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.

python setup.py dist_source

~~=== Activity sources ===~~

The tarball will be generated inside the dist directory.

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

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

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

shell.sugarlabs.org:/upload/sources/sucrose/fructose/(module_name)/

which translates to:

http://download.sugarlabs.org/sources/sucrose/fructose/(module_name)/

~~python setup~~.~~py dist_source~~

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

~~The tarball will be generated inside~~ the ~~dist directory~~.

=== Using the release script ===

For both, fructose and glucose components you can use the release script in [http://git.sugarlabs.org/projects/sugar-tools sugar-tools] to do the above tasks in one go.

== Sugar release ==

@@ Line 37: / Line 37: @@
 More in detail:
-* Build a source tarball, 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 glucose modules is:
+=== Glucose ===
-  shell.sugarlabs.org:/pub/sugarlabs/sources/sucrose/glucose/(module_name)/
+* Build a source tarball
+ make distcheck
+* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v0.81.9).
+* 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 glucose modules is:
+  shell.sugarlabs.org:/upload/sources/sucrose/glucose/(module_name)/
 which translates to:
   http://download.sugarlabs.org/sources/sucrose/glucose/(module_name)/
-The preferred location for fructose components is:
- 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).
 * 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.
-Note: You can use the release script in [http://git.sugarlabs.org/projects/sugar-tools sugar-tools] to do the above tasks in one go.
+=== Fructose ===
+* Build a source tarball
+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.
+ python setup.py dist_source
-=== Activity sources ===
+The tarball will be generated inside the dist directory.
-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.
+* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v20).
+* 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:
+ shell.sugarlabs.org:/upload/sources/sucrose/fructose/(module_name)/
+which translates to:
+ http://download.sugarlabs.org/sources/sucrose/fructose/(module_name)/
-  python setup.py dist_source
+* 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.
-The tarball will be generated inside the dist directory.
+=== Using the release script ===
+For both, fructose and glucose components you can use the release script in [http://git.sugarlabs.org/projects/sugar-tools sugar-tools] to do the above tasks in one go.
 == Sugar release ==