Changes

Jump to navigation Jump to search
Line 51: Line 51:     
Once your patch has received a 'r+', the reviewer will push your code to the repository. From now on your code is part of the Sugar code base and the community will maintain it for you.
 
Once your patch has received a 'r+', the reviewer will push your code to the repository. From now on your code is part of the Sugar code base and the community will maintain it for you.
  −
== Buildbot ==
  −
  −
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 check 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 use the jhbuild [http://dev.laptop.org/git?p=sugar-jhbuild;a=blob;f=scripts/data/pylintrc pylint configuration], to lint the files your patch modifies.
      
== Remind the maintainers about patches ==
 
== Remind the maintainers about patches ==
647

edits

Navigation menu