| [ << Administrative policies ] | [Top][Contents][Index][ ? ] | [ LilyPond grammar >> ] | ||
| [ < Overview of Patchy ] | [ Up : Automated testing with Patchy ] | [ > ] | ||
14.4.2 Patchy requirements
| [ << Administrative policies ] | [Top][Contents][Index][ ? ] | [ LilyPond grammar >> ] | ||
| [ < Patchy requirements ] | [ Up : Automated testing with Patchy ] | [ > ] | ||
Testing new patches
- A full local copy of the source code. See Working with source code.
- All the software needed for compiling LilyPond and the documentation. Although being able to build the full set of LilyPond’s manuals is not mandatory for testing (most) patches, part of the patch testing process requires that the regression tests are run and it is this that requires the software normally used for compiling documentation. See Compiling.
- Commit access is not required to test patches, but a valid login to http://code.google.com/ is.
| [ << Administrative policies ] | [Top][Contents][Index][ ? ] | [ LilyPond grammar >> ] | ||
| [ < ] | [ Up : Automated testing with Patchy ] | [ Installing Patchy > ] | ||
Testing & pushing new commits
- A full local copy of the source code. See Working with source code.
- All the software needed for compiling LilyPond and the documentation. Unlike testing patches, being able to build the full set of LilyPond’s documentation is required to be able to test & push new commits. See Compiling.
- Commit access is required to test and push new commits, but a valid login to http://code.google.com/ is not. See Commit access.
| [ << Administrative policies ] | [Top][Contents][Index][ ? ] | [ LilyPond grammar >> ] | ||
| [ < ] | [ Up : Automated testing with Patchy ] | [ Installing Patchy > ] | ||