Page History

...

Fix / implement JIRA ticket in your fork. Provide Java docs whenever required. If you add a new package make sure that package-info.java file in it is in place with a description. Commit branch to origin (origin = your fork). It's recommended to develop IGNITE-xxx ticket at ignite-xxx branch.
Create pull request from the new remote branch in the fork to master of Apache Ignite mirror. Please, start a title of the pull request from 'IGNITE-xxx'. An email about the pull request will be send to dev-list and the same JIRA comment will be added to the IGNITE-xxx ticket.
Trigger all the test suites validation on TeamCity:
- Locate "Run All" row and press on "Run" button. If you're sure that there is no need to check all the suites then trigger a particular test suite only;
- Go to "Changes" tab and choose "pull/<pull-request-number>/head" in "Build branch" dropdown list;
- Press "Run build" button and monitor tests results.
Once tests are passed, the pull request can be reviewed and merged by a committer.

...

List of points should be checked before push:

Javadoc

Make sure project build log contains no javadoc warnings. Grep build output for "Javadoc Warnings".
Check that every new package contains package-info.java file in it with a description.

In case new module added, make sure module contains README.txt at module's root.

...