Alawn/Chronicle-Map
1
0
Fork 0
mirror of https://github.com/OpenHFT/Chronicle-Map.git synced 2021-09-13 01:26:12 +00:00
Code Releases Activity

Document types of dependencies which could be updated without bumping Chronicle Map version

Browse Source
This commit is contained in:
leventov
2016-01-10 23:54:19 +03:00
parent 85939d6335
commit d283ebd6ef
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/versioning.md
+5 -1
View File
@@ -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