This is just a leaflet for the merge order of the latest PRs. The ones in italics are optional (wontfix tags indicate, they have worse performance if included).
Some brances are originated from others. E.g. branch which belongs to #202 have several childbranches (#204, #205, #206).
198 (MS5 initial commit) <- #202 (read-write locks in the persistent storage and storage units) <- #204 (bugfix in the commit ready phase of transactions) <- #216 (sorted entries)
198 (MS5 initial commit) <- #212 (KVServer CLI handling refactored) <- #213 (heartbeat messages are optional from KVServer, to ease testing without loadbalancer)
202 (read-write locks in the persistent storage and storage units) <- #206 (load storage units from persisted storage's root path on startup)
202 (read-write locks in the persistent storage and storage units) <- #205 (always load storage unit from disk, except it has free space)
benedekh
commented
7 years ago
This is just a leaflet for the merge order of the latest PRs. The ones in italics are optional (wontfix tags indicate, they have worse performance if included).
Some brances are originated from others. E.g. branch which belongs to #202 have several childbranches (#204, #205, #206).
198 (MS5 initial commit) <- #202 (read-write locks in the persistent storage and storage units) <- #204 (bugfix in the commit ready phase of transactions) <- #216 (sorted entries)
198 (MS5 initial commit) <- #212 (KVServer CLI handling refactored) <- #213 (heartbeat messages are optional from KVServer, to ease testing without loadbalancer)
202 (read-write locks in the persistent storage and storage units) <- #206 (load storage units from persisted storage's root path on startup)
202 (read-write locks in the persistent storage and storage units) <- #205 (always load storage unit from disk, except it has free space)