Versioning

TinkerPop follows a common versioning scheme for all projects, where the scheme follows:

x.y.z

Generally speaking, this means:

1. The documentation must be “the same” between all versions of .z (up to tweaks and clarifications, etc. — as the master/ branch is at .y)
2. External APIs are non-breaking for all .z versions.
3. Minor API changes are okay (preferably via Deprecated) up to @.y
4. Major API changes are okay up to x.
5. Bug fixes/optimizations/and very minor features are okay for the .z lines.
6. Features that need to be documented go into the .y line.
7. All .z versions of software must integrate — e.g. Frames 2.3.1 and Blueprints 2.3.0 must work together.

For new projects coming into TinkerPop, the following versioning convention is used.

0.x

Once the fledgling project is mature enough, it joins the main TinkerPop version sync.