Info |
---|
This is a proposed way of working, under discussion on the mailing list. See http://markmail.org/message/xoyjw2sduenlytwm Commit to master through PR only was decided on here: http://comments.gmane.org/gmane.comp.apache.cloudstack.devel/62223 |
Apache CloudStack is a broad and encompassing project covering many areas that require in-depth technical knowledge. As such, it is not possible for one person to know and/or test all components of CloudStack in depth. Miscommunications and misunderstandings between developers can lead to poor quality in CloudStack's code and cause community to deliver a unstable release. Knowledge lost from one release to the next can cause regressions in the current release. This page details the development process the CloudStack community must follow in order to ensure the community delivers high quality releases. This page is a must read for all developers and testers.
...
The process is very simple.
...
...
Q: I'm a contributor and not a committer. How do I participate in this process?
A: We will attempt to add a way to pull the source code from github as well. In the mean time, you should submit your changes as a patch via the review board. A reviewer will start a branch, apply the patch, wait for CI to pass, and merge it in for youYou can send a pull request on github. When two other collaborators give a LGTM, a committer will merge your pull request.
Q: Who is providing this jenkins?
...