Development Team/Release: Difference between revisions
remove sugar-tools release script, as it has not been maintained, and was not used for the 0.111 and 0.112 release, a new maintainer for sugar-tools is welcome |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 53: | Line 53: | ||
* 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 a 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 a 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. | * 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. | ||
* One week later, check that the corresponding packages have been updated, and if not contact the downstream packager. | |||
{{Anchor|Fructose}} | {{Anchor|Fructose}} | ||
===<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, | ||
* Increment the version number in the activity/activity.info metadata file, | |||
* Update any NEWS file with a list of changes, intended for a teacher or integrator, | |||
* 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: | * 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 | ||
| Line 71: | Line 74: | ||
* Push the release tag to the project repository, | * Push the release tag to the project repository, | ||
git push --tags | git push --tags | ||
* Upload the bundle to activities.sugarlabs.org, with a high level, | * Upload the bundle to activities.sugarlabs.org, with a high level, learner oriented list of changes, which will cause a release mail to be sent to sugar-devel@lists.sugarlabs.org. | ||
== Sugar release cycle== | == Sugar release cycle== | ||
| Line 151: | Line 154: | ||
Each commit or set of commit should have a ticket associated. The ticket number should be always mentioned in the git log and is used to automatically build the list of module changes for the releases. | Each commit or set of commit should have a ticket associated. The ticket number should be always mentioned in the git log and is used to automatically build the list of module changes for the releases. | ||
==Related pages== | ==Related pages== | ||