[
https://issues.apache.org/jira/browse/OAK-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251863#comment-15251863
]
Davide Giannella commented on OAK-4243:
---------------------------------------
this will definitely help us maintaining the previous branches.
Speaking of: is there anything {{oak-upgrade}} related we have-to/can think of
if we would like to deploy the new segment on top of 1.0, 1.2 or 1.4?
/cc [~tomek.rekawek]
> Oak Segment Next Module
> -----------------------
>
> Key: OAK-4243
> URL: https://issues.apache.org/jira/browse/OAK-4243
> Project: Jackrabbit Oak
> Issue Type: Epic
> Components: segment-next
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Fix For: 1.6
>
>
> There is a couple of issues requiring us to change the segment format in a
> non compatible way (OAK-3348, OAK-2896, OAK-2498, OAK-4201).
> We should introduce a new module here
> * to minimise ripple effect on concurrent development work in other parts of
> Oak and upstream projects
> * to be able to cleanly migrate existing repositories via a side grading
> * to cleanly separate breaking changes from the existing code base
> The plan is roughly to:
> * Create new module (called {{oak-segment-next}} for now, will discuss names
> later)
> * Apply patch prepared for OAK-3348
> * Discuss and decide on final name and refactor accordingly
> * Reactor affected tooling such that the targeted segment store can be
> specified via an option. Keep default at {{oak-segment}}.
> * Once sufficiently stabilised, deprecate {{oak-segment}}. Make this one the
> default in switch the default target for tooling.
> * Define and implement migration path
> I will create respective issues as needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
