Changes

* Have a public system for reporting and managing bugs in your activity. This is an invaluable resource for us when we are reviewing your activity as it gives us information on any problems in your activity.  We recommend using http://dev.sugarlabs.org .

* Have a public system for reporting and managing bugs in your activity. This is an invaluable resource for us when we are reviewing your activity as it gives us information on any problems in your activity.  We recommend using http://dev.sugarlabs.org .

* If possible, conduct a beta release cycle from your website every time you want to release a new version of your activity. Allow your current users to be involved, but be sure to warn them that the activity is in beta ;) Conducting a beta cycle will ensure your activity has less bugs and is of a higher quality when you release it and/or release new versions.

* If possible, conduct a beta release cycle from your website every time you want to release a new version of your activity. Allow your current users to be involved, but be sure to warn them that the activity is in beta ;) Conducting a beta cycle will ensure your activity has less bugs and is of a higher quality when you release it and/or release new versions.

* Have a public forum for users to critique, comment on and discuss your activity. If this is not possible or impractical, create a page on [[Activities | Activities]] about your activity - this will group together any comments that users have about your activity and allow reviewers to gather information about your activity more speedily.

* Have a public forum for users to critique, comment on and discuss your activity. If this is not possible or impractical, create a page on [[Activities]] about your activity - this will group together any comments that users have about your activity and allow reviewers to gather information about your activity more speedily.

* If you are updating your activity, have a changelog. This will inform us what parts of the activity have changed and which parts we especially need to test and give extra scrutiny to.

* If you are updating your activity, have a changelog. This will inform us what parts of the activity have changed and which parts we especially need to test and give extra scrutiny to.

* If any software is required for your activity, please state this in your submission.

* If any software is required for your activity, please state this in your submission.

* Only declare compatibility with Sugar versions and operating systems that you have tested with.

* Only declare compatibility with Sugar versions and operating systems that you have tested with.

* Comply with [http://activities.sugarlabs.org/pages/policy Activity Policy]]. They're only drafts at the moment, but we still enforce them.

* Comply with [http://activities.sugarlabs.org/pages/policy Activity Policy]. They're only drafts at the moment, but we still enforce them.

* Do not use Library Editors as beta testers and bug finders. This is not the purpose of editors. Please test the activity extensively before submitting.

* Do not use Library Editors as beta testers and bug finders. This is not the purpose of editors. Please test the activity extensively before submitting.