Development Team/Release: Difference between revisions

Line 39:

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> (base) modules===

* ~~Build a source tarball~~

* Check out the repository branch,

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

~~make distcheck~~

git tag v0.111

* Build a source tarball from the branch,

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

make distcheck

* Test the source tarball carefully, using {{Code|configure}}, {{Code|make}}, {{Code|make install}}, and any packaging technology you are familiar with,

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

* Upload the source tarball to a stable location. You need a developer account with Sugar Labs to be able to upload there. The location for glucose modules is:

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

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

which translates to:

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

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

* Push the release tag to the project repository,

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

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

* When the {{Code|sugar}} module is released, update the Activity Library default stable release; the variable {{Code|SITE_SUGAR_STABLE}} in site/app/config/config.php then check on [https://activities.sugarlabs.org activities.sugarlabs.org] with a browser other than Browse that an activity compatible with the release is listed.

* ~~Update~~ the Activity Library default stable release; the variable SITE_SUGAR_STABLE in site/app/config/config.php then check on activities.sugarlabs.org with a browser other than Browse that an activity compatible with the release is listed.

@@ Line 39: / Line 39: @@
 {{Anchor|Glucose}}
 === <abbr title="Glucose, the base Sugar environment">Glucose</abbr> (base) modules===
-* Build a source tarball
+* Check out the repository branch,
+* Create a git tag to reference the release.  The tag should be in the vXXX form (for example v0.111).
- make distcheck
+ git tag v0.111
+* Build a source tarball from the branch,
-* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v0.81.9).
+  make distcheck
+* Test the source tarball carefully, using {{Code|configure}}, {{Code|make}}, {{Code|make install}}, and any packaging technology you are familiar with,
-* 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:
+* Upload the source tarball to a stable location. You need a developer account with Sugar Labs to be able to upload there. The location for glucose modules is:
-  shell.sugarlabs.org:/upload/sources/sucrose/glucose/(module_name)/
+  shell.sugarlabs.org:/upload/sources/sucrose/glucose/ (module_name)/
 which translates to:
-  http://download.sugarlabs.org/sources/sucrose/glucose/(module_name)/
+  http://download.sugarlabs.org/sources/sucrose/glucose/ (module_name)/
+* Push the release tag to the project repository,
-* 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.
+* Announce by 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.
+* When the {{Code|sugar}} module is released, update the Activity Library default stable release; the variable {{Code|SITE_SUGAR_STABLE}} in site/app/config/config.php then check on [https://activities.sugarlabs.org activities.sugarlabs.org] with a browser other than Browse that an activity compatible with the release is listed.
-* Update the Activity Library default stable release; the variable SITE_SUGAR_STABLE in site/app/config/config.php then check on activities.sugarlabs.org with a browser other than Browse that an activity compatible with the release is listed.
 {{Anchor|Fructose}}