...
Panel | ||
---|---|---|
| ||
A change is a portion of code submitted to https://gerrit.onap.org. Sometimes referred to as a 'gerrit' or patch, it is essentially a git commit pushed to gerrit code review system. |
Committer Promotion Prerequisites
ONAP membes seeking promotion to committer status should demonstrate the following abilities and behaviours before being considered for promotion. Ideally the individual has been participating in the community and several projects including the one they are seeking promotion to. Contributors can perform 95% of the duties of a formal committer including the following which would be expected from both contributors and committers.
- JIRA involvement - including one or more of raising, reviewing, commenting, testing, linking, attaching to, answering questions on, closing JIRAs
- Confluence invol
- Git involvement - being able to clone, build, patch, commit and run the code in their project and ideally any of the north or southbound dependend projects
- Knowledge of the architecture and API of the project - ideally across ONAP
- Participation in onap-discuss work including helping with issues, raising issues
Best Practices
- Committers should not "self merge" their own changes
- Committers should add other committers as reviewers and have at least 2 Committers show approval (with a +1). The first reviewing committer will +1, the second reviewing committer will +2.
- One exception to the rule is self merging critical changes required to unblock broken builds.
- Committers should only merge proposed changes from contributors after at least 2 (+1) reviews.
- Committers should remove themselves from a review under the following circumstances:
- Committer has been added as a reviewer to a change they do not feel comfortable reviewing
- Committer anticipates a lack of time to review within 1 week
- Committers who remove themselves should leave a short comment in the change explaining to the owner the reason for removal
- This allows owners opportunity to find others willing to review (or to make changes to significantly simplify or further document change)
- Committers should aim to review all pending changes which have passed verify, have no merge conflicts or (-1) or (-2) reviews in a timely manner.
- Committers are welcome to ignore pending changes which do not pass verify, have merge conflicts or have been reviewed (-1) or (-2).
- Committers should occasionally review the list of all old changes (To be defined). Owners of old changes should be contacted to ascertain if the change can be abandoned. If change owners do not respond or respond that the change has been abandoned, it should be abandoned.
...