THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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
- subscribing and sending a message to the <dev-flume AT SPAMFREE incubator DOT apache DOT org> Flume developer mailing list,.
- filing a bug report in getting an account and filing an issue in the Apache 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 Almost all patches should include unit tests or modifications to unit tests. Big cross-cutting changes should be discussed ahead of time, some up front design documentation and consideration for backwards compatibility 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.
- You can use
svn stat
to see which
- files have been modified,
svn add
to add the files for commit, and thensvn diff > FLUME-###.patch
to generate a patchfile. - You can use
git status
to see which files have been modified,git add
to add files for commit, and thengit format-patch
to generate a git patchfile.
- You can use
- 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, (usually formatting, correctness review as well as request for docs or follow on issues).
- When it's ready, a committer will push it to the repository and mark the issue as "Resolved/Fixed" in JIRA.
...
- Create a new account for yourself.
- Sign up for the "Flume" review group if you would like to receive email when new patches are posted. (Reviews are also posted to the flume-dev mailing list.)
- SVN:
- Create a new review. This requires creating a diff against the master branch and then uploading the patch. The patch base path should usually be
/
- The repository should be set to "flume".
- Add the group "flume" to the Reviewer Groups list (otherwise we won't see it).
- Describe your changes and the test plan you implemented and executed.
- Put the JIRA issue number (e.g., "FLUME-10") in the "bugs" list.
- Make sure to hit "Publish" when you're ready.
- Create a new review. This requires creating a diff against the master branch and then uploading the patch. The patch base path should usually be
- Git:
- Create a new review. This requires creating a diff against the master branch and then uploading the patch.
- The repository should be set to "flume-git".
- Add the group "flume" to the Reviewer Groups list (otherwise we won't see it).
- Describe your changes and the test plan you implemented and executed.
- Put the JIRA issue number (e.g., "FLUME-10") in the "bugs" list.
- Make sure to hit "Publish" when you're ready.
...