THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Before committing a patch of one JIRA, you should first get +1 from at least 1 other committer.
- Also, the patch to be committed should have been run through a Precommit Build and obtained a +1 ( green light ) on the JIRA by the build job. This will happen automatically if the JIRA status has been set to Patch Available.
- The build job will add a comment to the JIRA after the patch has been tested.
- You should work on this repository which is writable https://git-wip-us.apache.org/repos/asf/tez.git
- Each patch requires a +1 from a committer. If the author of the patch is a committer, it requires a +1 from a different committer.
How to Commit
- First you need to ask yourself, which branch you need to commit into ? Usually you should commit it to master, if there's one release based on another branch, you should also commit into that branch ( use cherry-pick as below ). If you are not sure about this , send a message to the Tez developer mailing list.
- For each commit, you should also update the CHANGES.txt, including which release this JIRA will go in and add details to the INCOMPATIBLE CHANGES section if it is an incompatible change. Our convention is to put your change on the top of change list.
- Any patch that is applied and committed should have been previously uploaded to JIRA by the author. In certain scenarios, when fixing minor nits, the committer can make a change, upload the patch with the minor modification to JIRA and then commit the modified patch.
...