Activity Team/Packaging: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
=== Publish source tarballs for each release === | === Publish source tarballs for each release === | ||
''If your activity is part of Fructose | ''If your activity is part of Fructose follow [[Development Team/Release#Module_release|Module Release]] instead.'' | ||
* | * Make a source tarball as follows. It will be placed inside the dist/ directory. | ||
python setup.py dist_source | |||
* Upload it on the web. If you need a server to upload it to, | * Upload it on the web. If you need a server to upload it to, [[Service/shell|ask for a shell account]]. When you have access, create a directory under /upload/sources/honey for your activity and copy the tarball to it. | ||
* Update the Honey table on the [[Development Team/Source_Code#Honey|Source Code]] page with a link to the latest version. | * Update the Honey table on the [[Development Team/Source_Code#Honey|Source Code]] page with a link to the latest version. Add an entry if your activity is not yet listed. | ||
=== Create a trac component for your activity === | === Create a trac component for your activity === | ||
Users or packagers may report problems with your activity, either; | |||
* enable the Issues feature in the GitHub repository, or; | |||
* open a ticket on http://bugs.sugarlabs.org, under the trac component, to request a ''component'' for your activity. | |||
=== Check copyright and licensing === | === Check copyright and licensing === | ||
* Many translations | * Many translations lack copyright and licensing info completely or they provide just a boilerplate.The package maintainer should edit the .pot file to replace these: | ||
SOME DESCRIPTIVE TITLE | SOME DESCRIPTIVE TITLE | ||