You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
1 Communication
- The communication channel of record is dev@pekko.apahce.org
- All discussion concerning changes must occur on the dev@pekko.apache.org mailing list. If it is not on the mailing list it did not happen.
- Apache Pekko follows the Apache voting rules: https://www.apache.org/foundation/voting.html
2 Development
- Defects are recorded in the git issue for the associated Pekko module.
- All changes to release branches must be made via pull requests.
- All pull requests for code changes (e.g. changes that modify the code execution)
- must be associated with an issue.
- must be reviewed and approved by at least two committers who are not the developer(s).
- must be voted on in the development list using the code modifications process documented in the Apache voting process document
- Trivial documentation changes (e.g. spelling errors, javadoc errors) are changes that do not affect code execution.
- Trivial documentation changes may be approved by one committer who may also be the editor.
- Trivial documentation changes do not require discussion in the mailing list.
- Substantive documentation changes (e.g. not trivial)
- must be associated with an issue
- must be reviewed and approved by at least two committers who are not the editor(s).
- must be voted on in the development list using the code modifications process documented in the Apache voting process document.
3 Process Changes
- All processes are recorded in this wiki.
- Processes may be changed by the process specified in the Apache voting process document section on procedural issues.