Line 4: |
Line 4: |
| == ASLO auto checking == | | == ASLO auto checking == |
| | | |
− | * unique ''bundle_id'' activity.info field value | + | * Unique ''bundle_id'' activity.info field value |
− | * unique ''name'' activity.info field value | + | * Unique ''name'' activity.info field value |
| * ''license'' activity.info field value has short names that conform fedora good licences lists: [http://fedoraproject.org/wiki/Licensing#Good_Licenses software], [http://fedoraproject.org/wiki/Licensing#Good_Licenses_2 documentation] and [http://fedoraproject.org/wiki/Licensing#Good_Licenses_3 content]. | | * ''license'' activity.info field value has short names that conform fedora good licences lists: [http://fedoraproject.org/wiki/Licensing#Good_Licenses software], [http://fedoraproject.org/wiki/Licensing#Good_Licenses_2 documentation] and [http://fedoraproject.org/wiki/Licensing#Good_Licenses_3 content]. |
− | * activity version is an integer number | + | * Activity version is an integer number |
| + | * Check if activity has correct link to bugs tracker |
| + | * Activity version has release notes |
| | | |
| == Technical policy == | | == Technical policy == |
Line 16: |
Line 18: |
| ** x86_64 architecture (looks like we have x86_64 only for SP-0.84+) | | ** x86_64 architecture (looks like we have x86_64 only for SP-0.84+) |
| * If activity entirely(not just minor glitches like screen resolution) depends on hardware/software properties of particular environment(XO for example), this activity can not be pushed to the public and should be left in [[Glossary#Experimental_activity|Experimental]] stage. In that case editors could collect these activities in collections e.g. "Experimental XO activities" until they are fixed to run in common environment which satisfy Sugar Platform specification. | | * If activity entirely(not just minor glitches like screen resolution) depends on hardware/software properties of particular environment(XO for example), this activity can not be pushed to the public and should be left in [[Glossary#Experimental_activity|Experimental]] stage. In that case editors could collect these activities in collections e.g. "Experimental XO activities" until they are fixed to run in common environment which satisfy Sugar Platform specification. |
− | * Check if activity has correct link to bugs tracker
| |
| * Check it there is a component for activity on [https://bugs.sugarlabs.org/ bugs.sugarlabs.org] (or whatever was set as bugs tracker), if not, ask uploader about maintainer and create(request for creation) one | | * Check it there is a component for activity on [https://bugs.sugarlabs.org/ bugs.sugarlabs.org] (or whatever was set as bugs tracker), if not, ask uploader about maintainer and create(request for creation) one |
| * For all bugs, that were found during review, create bug tickets | | * For all bugs, that were found during review, create bug tickets |