jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-3613) Backport TarMK revision gc related issues
Date Mon, 16 Nov 2015 11:25:11 GMT

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

Michael Dürig commented on OAK-3613:

* I didn't back port OAK-3125 as it also requires OAK-3052 and the latter depends on OAK-2870.
This seemed too much for a nice to have. 

* OAK-3506 produced a lot of conflict so I skipped it. Since it is low risk I can try again
reimplementing the conflicting bits. 

> Backport TarMK revision gc related issues
> -----------------------------------------
>                 Key: OAK-3613
>                 URL: https://issues.apache.org/jira/browse/OAK-3613
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: segmentmk
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: compaction, gc
>             Fix For: 1.2.8, 1.0.24
> Some of the issues related to TarMK revision gc should be back ported to the branches.
This issue is for keeping track of which issues and which svn revisions we consider for back
porting. The task consists of the following steps:
> # Identify issue to back port
> # Merge the respective commits into a private forks of the 1.0 and 1.2 branches
> # Run tests on builds from the private forks
> # On success merge the private forks to the 1.0 and 1.2 branches and update the fix versions
of the respective issues. This probably requires manually updating the svn merge info with
the respective svn revisions. 
> [~dhasler]: FYI
> [~alex.parvulescu], [~frm]: please refrain from merging potential conflicting changes
into the branches in the meanwhile. 

This message was sent by Atlassian JIRA

View raw message