On 21.10.16 3:04 , Julian Sedding wrote:
an arguably simpler solution would be to give oak-run and oak-upgrade a separate lifecycle. They are consumers of both segment-tar and oak-core (+ other bundles with same release cycle). Hence they require interoperable releases of both *before* they themselves can be released.
+1. This would match the requirement for Segment Tar as it allows for running upgrades and tools against specific versions. Something that is indispensable for effective and continuous monitoring of performance, disk foot print and memory usage and for efficiently identifying regressions in any of these areas.
Michael
