THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
- Every JIRA ticket should be sufficiently described.
- There should not be any tickets with title only and without description.
- If there is a discussion pertaining to the ticket, the ticket should have a link to the dev list.
...
Working on Tickets
- Anyone in the community can start working on any unassigned ticket.
- (OPTIONAL) It is recommended to clarify the relevance and correctness of the ticket in the community before doing actual implementation. To do this, you can write an email to the dev.list and wait for answer.
- Before beginning working on a ticket, you should assign the ticket to yourself.
- Move the ticket to
IN PROGRESSstate. - If necessary, add comments describing the design decisions or approach you plan to take.
- If the changes implemented under the ticket require changes in user documentation, create a related documentation ticket (add "Documentation" to the Component field) and provide a reasonable amount of details in the ticket's description. If there is no need to change user documentation, uncheck the Docs Required flag.
Review Process and Maintainers
...
Changes to a CTR module (CTR*) may be merged without waiting for review by a maintainer. However it's advisable to ask a maintainer of a CTR module for review and to wait for some time for his/her feedback.
| Component | Maintainers |
|---|---|
| Ignite Core (data grid, rebalancing, affinity, the rest of internals not covered below) | Semen Boikov, Alexey Goncharuk, Yakov Zhdanov, Anton Vinogradov |
| Marshalling (Binary, Optimized, JDK) | Vladimir Ozerov, Denis Magda, Alexey Goncharuk |
| Discovery & Communication SPIs | Yakov Zhdanov, Semen Boikov, Denis Magda |
| Ignite Compute API | Yakov Zhdanov, Valentin Kulichenko |
| Ignite Services API | Valentin Kulichenko |
| Ignite SQL & Text Queries | Sergey Vladykin |
| Ignite Continuous Queries | Nikolai Tikhonov, Semen Boikov |
| Build System | Anton Vinogradov |
| Hadoop Accelerator | Vladimir Ozerov, Ivan Veselovsky |
| Spark Shared RDDs | Alexey Goncharuk, Andrey Gura |
| IGFS | Vladimir Ozerov, Ivan Veselovsky |
| .Net API | Pavel Tupitsyn, Vladimir Ozerov |
| C++ API | Igor Sapego, Vladimir Ozerov |
| Streamers (JMS, Flume, Kafka, etc.) CTR* | Raúl Kripalani, Roman Shtykh |
| Docker, Mesos, YARN integration | Nikolai Tikhonov |
| AWS, Google Compute Engine, JClouds integration | Denis Magda, Nikolai Tikhonov |
| OSGi integration | Raúl Kripalani, Denis Magda |
| Visor | Alexey Kuznetsov |
| WebSession & WebSession Filter | Valentin Kulichenko |
Submitting for Review
- Attach a patch, pull request url or branch name (see instructions at Workflow)
- (OPTIONAL) create an Upsource review: Review With Upsource
- Add comment describing what has been implemented.
- Move ticket to
PATCH AVAILABLEstate.
...
Overview
Content Tools
Apps