You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2016/07/19 08:16:20 UTC

[jira] [Commented] (OAK-4247) Deprecate oak-segment

    [ https://issues.apache.org/jira/browse/OAK-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383771#comment-15383771 ] 

Michael Dürig commented on OAK-4247:
------------------------------------

[~frm] assigning to you for now as you did all the ground work for the {{oak-segment-tar}} release. I think the only thing left to do here is to actually mark {{oak-segment}} and its classes as deprecated. I think we should do this as soon as we see the {{oak-segment-tar}} releases are stable enough to serve as a replacement. 

> Deprecate oak-segment
> ---------------------
>
>                 Key: OAK-4247
>                 URL: https://issues.apache.org/jira/browse/OAK-4247
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: segment-tar, segmentmk
>            Reporter: Michael Dürig
>            Assignee: Francesco Mari
>            Priority: Critical
>              Labels: technical_debt
>             Fix For: 1.6, Segment Tar 0.0.6
>
>
> Before the next major release we need to deprecate {{oak-segment}} and make {{oak-segment-tar}} the new default implementation:
> * Deprecate all classes in {{oak-segment}}
> * Update documentation to reflect this change
> * Update tooling to target {{oak-segment-tar}} (See OAK-4246). 
> * Update dependencies of upstream modules / projects from {{oak-segment}} to {{oak-segment-tar}}. 
> * Ensure {{oak-segment-tar}} gets properly released (See OAK-4258). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)