[
https://issues.apache.org/jira/browse/OAK-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008452#comment-15008452
]
Michael Dürig edited comment on OAK-3613 at 11/17/15 10:33 AM:
---------------------------------------------------------------
Thanks for the review Alex!
* OAK-1446: I think we should merge this unless it turns out as too messy, will
have a look.
* OAK-3123: Just merged a minute ago ;-)
* OAK-3235: I initially considered this one. But it has nasty dependencies. I
consider this one not critical but the regression risk too high, so I'd rather
leave it out.
OAK-2674 and OAK-1995: Can we try to pull changes introduced by those in where
necessary? Risk should be low.
was (Author: mduerig):
Thanks for the review Alex!
* OAK-1446: I this we should merge this unless it turns out as too messy, will
have a look.
* OAK-3123: Just merged a minute ago ;-)
* OAK-3235: I initially considered this one. But it has nasty dependencies. I
consider this one not critical but the regression risk too high, so I'd rather
leave it out.
OAK-2674 and OAK-1995: Can we try to pull changes introduced by those in where
necessary? Risk should be low.
> 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.9, 1.0.25
>
> Attachments:
> 0001-OAK-2870-Introduce-a-SegmentNodeStoreBuilder-to-help.patch,
> 1.2-OAK-2870.patch
>
>
> 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.
> * Update the svn merge info with the respective merged svn revisions.
> * Update the fix versions of the affected issues.
> [~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
(v6.3.4#6332)
