THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- If you are new to Tez and want to start with pre-existing issues, look for Jiras labeled newbie.
- Once, you have found an unassigned issue to work on, add a comment stating your interest to work on the issue and one of the committers will assign the issue to you.
- When making changes, follow the same coding style as the code that you are modifying.
- Please ensure that each line remains with a 100-char limit.
- Ensure that all newly added code is documented well with javadocs as appropriate.
- Add unit tests for your code.
Submitting a Patch
- Once you have made the required changes, ensure that the code compiles and all the unit tests run successfully.
- Now, you can generate a patch using "git diff --no-prefix origin/master" ( Use "origin/branchname" to generate a diff against a different branch.
- Name the patch file using the JIRA issue and a patch version or a datetime when the patch was generated. For example, "TEZ-1234.1.patch" or "TEZ-1234.20140516.1.patch"
- Add the branch name to patch filename in case the patch is generated for a branch other than master.
- Attach this patch file to the JIRA issue and hit "Submit Patch" to change the issue status to "Patch Available". This will trigger a utility that will test the patch by applying it, checking for various issues ( new warnings, findbugs, new tests added, etc) and also run unit tests after applying the patch.
- If you do not see any feedback on your patch within a couple of days, please send a friendly reminder mail to the dev mailing list.
...