Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Anyone in the community may start working on any Unassigned ticket. 
  • (OPTIONAL) It is recommended to clarify the relevance and correctness of the ticket with the community before doing actual implementation. To do this, you can write an email to the dev mailing list and wait for an answer (please do not forget to subscribe to the list first).
  • Before beginning working to work on a ticket, you should assign the ticket to yourself.
  • Move the ticket to IN PROGRESS state.
  • If necessary, add comments describing the design decisions or approach approaches you plan to take.

Documenting a ticket

...

  • Attach Pull Request URL to ticket (see instructions at Workflow)
  • Add a comment describing what has been implemented.
  • Run tests using Run All... TeamCity suite. Validate that all tests have passed using TeamCity bot. It allows checking that no new non-flaky tests have failed, and posting the confirmation ("TC green visa") to the ticket.
  • Move ticket to PATCH AVAILABLE state.
  • If you know a contributor who should review this ticket, you should mention them directly:

...

ComponentMaintainers
Ignite Core (the rest of internals not covered below)

PME

Rebalance

Affinity

PDS

Encryption

MVCC (obsolete)

Transactions

Snapshots
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

...