From d283ebd6efb65c1fa5dc66685eff62991ecc170e Mon Sep 17 00:00:00 2001 From: leventov Date: Sun, 10 Jan 2016 23:54:19 +0300 Subject: [PATCH] Document types of dependencies which could be updated without bumping Chronicle Map version --- docs/versioning.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/versioning.md b/docs/versioning.md index a51662797..293233d71 100644 --- a/docs/versioning.md +++ b/docs/versioning.md @@ -13,7 +13,11 @@ `ChronicleMapBuilder` configured the same way constructs a `ChronicleMap` with different number of segments, or segment's capacity, etc. - Any dependency is updated, even if only "patch" number is updated, e. g. `chronicle-bytes` - dependency is updated from `1.1.1` to `1.1.2`. + dependency is updated from `1.1.1` to `1.1.2`. This rule doesn't apply to dependencies to the + umbrella POMs which merely determine versions of other dependencies (namely `chronicle-bom` and + `third-party-bom`), if the versions of actual dependencies doesn't change between those versions + of umbrella POMs. Also, this rule doesn't apply to dependencies with `test` and `provided` Maven + scopes. - Bug fixing, performance optimization or feature addition requires to change the binary or serialized form of Chronicle Map data store (therefore revise the Chronicle Map data store specification, see below), or the binary replication protocol, or the serialized form of some