Line 58: |
Line 58: |
| ===<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 72: |
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, user oriented list of changes, which will cause a release mail to be sent to sugar-devel@lists.sugarlabs.org. | + | * 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== |