THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
Create a Ticket Branch (only for committers)
Creation & Applying
Whenever working on bigger features, committers can also create 'ready to be reviewed' branch ignite-XXXX, where XXXX is the number of the JIRA ticket.
...
The branch should be deleted on branch merged to master or issue canceled. Committers are in charge of deleting their branches.
Appendix A. Components and their maintainers
| Component | Maintainers | |
|---|---|---|
| Ignite Core (the rest of internals not covered below) | ||
| PME | ||
| Rebalance | ||
| Affinity | ||
| PDS | ||
| Encryption | ||
| MVCC (obsolete) | ||
| Transactions | ||
| Marshalling (Binary, Optimized, JDK) | ||
| Discovery & Communication SPIs | ||
| Ignite Compute API | ||
| Ignite Services API | ||
| Ignite SQL & Text Queries & JDBC | ||
| Ignite Continuous Queries | ||
| Machine Learning/Deep Learning (ml, TensorFlow, sub-modules in ml) | ||
| Build System / Releases | ||
| TeamCity Bot | ||
| Spark Integration | ||
| .NET API | ||
| C++ API | ||
| Other thin clients (Python, Node.js, PHP, etc) | ||
| ODBC | ||
| JDBC | ||
| Streamers (JMS, Flume, Kafka, etc.) | ||
| Docker, Mesos, YARN integration | ||
| AWS, Google Compute Engine, JClouds integration | ||
| Visor Console | ||
| WebSession & WebSession Filter | ||
...
Overview
Content Tools
Apps