Community SSU
(Flesh out.) |
m (Minor tweak) |
||
| Line 4: | Line 4: | ||
== Changelog == | == Changelog == | ||
| - | |||
{{main|Community SSU/Changelog}} | {{main|Community SSU/Changelog}} | ||
Changes in the SSU between PR1.3 and various SSU releases. | Changes in the SSU between PR1.3 and various SSU releases. | ||
| + | |||
| + | == QA and bugs == | ||
| + | {{main|Community SSU/QA}} | ||
| + | |||
| + | Quality is of paramount importance to the Community SSU. There are, therefore, two repositories: ''testing'' and ''stable''. Changes are carefully tested, with an extensive set of tests, before things are made "stable". | ||
| + | |||
| + | If you have found a bug, in either the ''testing'' or ''stable'' releases, please [http://bugs.maemo.org/ raise a bug]. Getting involved through testing, bug triaging and running of the tests is a good way to get involved; as, of course, is writing documentation! | ||
== Development == | == Development == | ||
| Line 13: | Line 19: | ||
{{main|Community SSU/Development}} | {{main|Community SSU/Development}} | ||
| - | The Community SSU is developed and managed through [http://gitorious.org/community-ssu Gitorious]. Bugs are tracked in [http://bugs.maemo.org/ Bugzilla]. | + | The Community SSU is developed and managed through [http://gitorious.org/community-ssu Gitorious]. Bugs are tracked in [http://bugs.maemo.org/ Bugzilla]. Getting involved through development, bug triaging and managing developers is a good way to get involved. |
[[Category:Community]] | [[Category:Community]] | ||
Revision as of 15:10, 20 January 2011
A place-holder for the in-development Fremantle community SSU.
More detail: contact MohammadAG on #maemo-ssu on FreeNode IRC.
Changelog
Main article: Community SSU/Changelog
Changes in the SSU between PR1.3 and various SSU releases.
QA and bugs
Main article: Community SSU/QA
Quality is of paramount importance to the Community SSU. There are, therefore, two repositories: testing and stable. Changes are carefully tested, with an extensive set of tests, before things are made "stable".
If you have found a bug, in either the testing or stable releases, please raise a bug. Getting involved through testing, bug triaging and running of the tests is a good way to get involved; as, of course, is writing documentation!
Development
Main article: Community SSU/Development
The Community SSU is developed and managed through Gitorious. Bugs are tracked in Bugzilla. Getting involved through development, bug triaging and managing developers is a good way to get involved.