[
https://issues.apache.org/jira/browse/OAK-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008704#comment-15008704
]
Francesco Mari commented on OAK-3613:
-------------------------------------
It looks good to me, but I have some doubt about the export version. How do we
usually handle the {{package-info.java}} files when backporting changes? I see
that multiple modifications where made to that package without updating the
{{package-info.java}}. Those modifications didn't change the API of the
package, but they should have changed at least the micro version. The change in
1693874 is changing the exported API of the package, so probably we should
update the exported version as well, most likely to 1.1.
> 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, 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
(v6.3.4#6332)
