-
-
Notifications
You must be signed in to change notification settings - Fork 718
Contributing to Soot
Currently, Soot follows the git-flow branching model. This means that there are two main branches, master and develop. Master usually only points to stable release versions. The latest branch that most people use is develop, which gets changed almost daily. Develop is merged into main on every release. Larger new features are maintained in topic branches which are then merged into develop once the feature becomes stable.
Our nightly tests and nightly builds all operate on develop.
To fix a problem in Soot or to contribute to Soot you can fork the Soot project on github. This will generate a new branch for you to work on in an own cloned repository. To reincorporate your changes into Soot after they have been completed and tested, just send us a pull request. This will allow us to review your changes and merge them into the develop branch.
If you have any queries regarding SOOT, then please refer to the following link bellow. First register yourself and start posting your questions and problems. Please try to ask question along with your reference code or problem which may be a bug or error in your code.
http://www.sable.mcgill.ca/mailman/listinfo/soot-list/
You can also see all of the queries posted previously and may be find your answer in these queries already.
Also check out Soot's webpage.
NOTE: If you find any bugs in those tutorials (or other parts of Soot) please help us out by reporting them in our issue tracker.
- Home
- Getting Help
- Tutorials
- Reference Material
- General Notions
- Getting Started
- A Few Uses of Soot
- Using Soot as a Command-Line Tool
- Using the Soot Eclipse Plugin
- Using Soot as a Compiler Framework
- Building Soot
- Coding Conventions
- Contributing to Soot
- Updating the Soot Web Page
- Reporting Bugs
- Preparing a New Soot Release