Page History

...

• Before you start, describe your proposed changes and check that they fit in with what others are doing and have planned for the project. Be patient, it may take folks a while to understand your requirements. This can be done by
  • sending a message to the <dev-flume AT SPAMFREE incubator DOT apache DOT org> Flume developer mailing list,
  • filing a bug report in Flume issue tracker JIRA, or
• Alternately, if you are interested in contributing you can find an existing issue one to work on. If you are just starting, we'd suggest you pick an "Easy" issue

• Assign the issue to yourself in the JIRA. If you cannot, ask one of the project administrators to add you as a contributor.
• Make your changes. These should include unit tests. Big changes should be discussed ahead of time, some up front design documentation may be necessary.
• Make sure your changes pass the required code quality metrics (see below)
• Create a single commit containing all your changes and a descriptive commit message (what files/classes did you add/remove; what tests did you add; what functionality does this include; etc). If you made multiple commits during your development process, squash them down to a single commit patch.
• Create a patch with your changes and commit message information:

  Code Block
  *TODO*

• Post patch to Reviewboard for code review. (see below)
• Upload patch to JIRA granting license to Apache and put link to specific code review to the in the comments.
• Update the issue in JIRA to reflect status "patch available".
• Iterate with revised changes, etc.
• When it's ready, a committer will push it to the repository and mark the issue as "Resolved/Fixed" in JIRA.

...