344
edits
Homepage | Activities | Events | Lists | Development | Translate | Contact
Changes
Jump to navigation
Jump to search
Line 39:
Line 39: − + Line 57:
Line 57: + + + +
Development Team/Code Review (view source)
Revision as of 06:47, 30 September 2009
, 06:47, 30 September 2009add section Dependencies
* note which module is effected e.g. sugar, sugar-toolkit...
* note which module is effected e.g. sugar, sugar-toolkit...
* note possible dependencies e.g. the patch is for sugar but depend on the current HEAD of sugar-toolkit which went in 5 seconds ago
* note possible dependencies e.g. the patch is for sugar but depend on the current HEAD of sugar-toolkit which went in 5 seconds ago (see also separate section about external dependencies below)
== Discussion ==
== Discussion ==
== Commit ==
== Commit ==
If you have commit access to the repositories you should read the [http://wiki.sugarlabs.org/go/Git#Git_commit_message_guidelines commit guidelines] as well before submitting your changes.
If you have commit access to the repositories you should read the [http://wiki.sugarlabs.org/go/Git#Git_commit_message_guidelines commit guidelines] as well before submitting your changes.
= Dependencies =
Dependencies need to be fulfilled on all platforms running Sugar (i.e. they need to be available at all and need to be installed which means occupying disk space), so think twice before introducing new ones. Please discuss them on [[Sugar Labs/Contacts#Developer Lists|sugar-devel]] in advance and clearly state them in the ticket. It's a always a good idea to check whether sufficiently recent versions of your proposed dependencies are already packaged for all (stable releases of the) major distributions, on '''all''' of their (semi-)supported architectures (e.g. ARM and PowerPC). If not, start requesting them (at the distribution bug trackers) ASAP and also mention it on sugar-devel and the ticket.
[[Category:Development Team]]
[[Category:Development Team]]