jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonas Oskö (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-3613) Backport TarMK revision gc related issues
Date Mon, 11 Jul 2016 12:23:11 GMT

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

Jonas Oskö commented on OAK-3613:


I am on vacation and will be back on Aug 15th. Meanwhile, please contact Jimmy Lundström
(jimmy.lundstrom@hm.com) for any CMS/AEM-related questions.

Best / Jonas

The information contained in this e-mail message may be privileged, confidential, and protected
from disclosure. Any unauthorized use, printing, copying, disclosure or dissemination of this
communication may be subject to legal restriction or sanction. If you think that you have
received this e-mail message in error, please reply to the sender and delete this message
from your computer.

> 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.0.33
>         Attachments: 0001-OAK-2870-Introduce-a-SegmentNodeStoreBuilder-to-help.patch,
1.2-OAK-2870.patch, OAK-1995-1.0.patch, OAK-1995-1.2.zip, OsgiUtil-1.0.patch, OsgiUtil-1.2.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

View raw message