[
https://issues.apache.org/jira/browse/OAK-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008439#comment-15008439
]
Alex Parvulescu edited comment on OAK-3613 at 11/17/15 10:48 AM:
-----------------------------------------------------------------
Some issues I noticed going through a diff between trunk and 1.0:
* OAK-1446 was resolved as duplicate but has a commit which never made it to 1.0
* OAK-3123 possible candidate
* OAK-2674 crosscutting issue. I'm really not sure what to do with this one
really.
* OAK-3235 possible candidate although very likely not a good one as it has too
many strings attached
* OAK-1995 was already mentioned (also takes care of removing unused
{{MergeDiff}} class)
* OAK-3158 got missed on the first pass
was (Author: alex.parvulescu):
Some issues I noticed going through a diff between trunk and 1.0:
* OAK-1446 was resolved as duplicate but has a commit which never made it to 1.0
* OAK-3123 possible candidate
* OAK-2674 crosscutting issue. I'm really not sure what to do with this one
really.
* OAK-3235 possible candidate although very likely not a good one as it has too
many strings attached
* OAK-1995 was already mentioned (also takes care of removing unused
{{MergeDiff}} class)
> 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)
