Page History

...

As a code contributor to Apache CloudStack, regardless of if you have committer or contributor status, your responsibilities are as follows:

Acquiring Knowledge

• Understand how to use JIRA to communicate your work with release managers, users, developers, and testers.
• Understand CloudStack's architecture and where you should or should not make changes.
• Understand CloudStack's simulator and how to run it and how to change it to test your code.
• Understand CloudStack's Marvin framework and how to use it to write automated tests.
• Understand CloudStack's code check-in process.
• Understand CloudStack's review process and your role in it as the reviewer and the code submitter.

JIRA

Communicating what issues you're working on and how you're working on it is an important part of participating in the community.  We do that on the mailing list.  However, you should use JIRA to update issue status and add comments with conclusions drawn from mailing list discussions.  This allows release managers, users, and testers to follow the issue better, to understand if the issue is being worked on, to get a better feel of whether an issue will be resolved in time for the release.

Writing Automated Tests

Automated tests ensures that your feature will not be regressed.  Anyone who submits a code change that breaks an existing automated test is responsible for fixing that automated test or revert the code change.  All automated tests should  

Continuous Integration

Maintaining CloudStack's Continuous Integration is the job of every developer.  

On Code Reviews

Infrastructures Provided

...