344
edits
Changes
Development Team/Code guidelines (view source)
Revision as of 06:36, 31 January 2010
, 06:36, 31 January 2010→Buildbot: currently buildbot is only running the test suites (no style checks), reflect that in the wording and show how to do the same
We are running periodic builds of Sugar using [http://buildbot.sugarlabs.org Buildbot]. If you break the build you are responsible to get it fixed. If you don't, the release team will take care of it, most likely by reverting your patch. More in detail:
We are running periodic builds of Sugar using [http://buildbot.sugarlabs.org Buildbot]. If you break the build you are responsible to get it fixed. If you don't, the release team will take care of it, most likely by reverting your patch. More in detail:
* Every change that causes build or check failures should be immediately fixed or reverted.
* Every change that causes build or test suite failures should be immediately fixed or reverted.
* Every change that causes check warnings should be fixed or reverted within 24 hours.
* Every change that causes pylint or PEP8 warnings should be fixed or reverted within 24 hours.
You can use the check command in jhbuild to execute the same checks that [http://buildbot.sugarlabs.org/ Buildbot] is doing.
You can pass the <code>--check</code> option to [[Development Team/Jhbuild|Jhbuild]] to execute the same checks that [http://buildbot.sugarlabs.org/ Buildbot] is doing:
./sugar-jhbuild buildone -n --check sugar-artwork
== References ==
== References ==