jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-6346) Set baseline plugin comparison version to 1.6.0
Date Mon, 10 Jul 2017 09:16:02 GMT

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

Marcel Reutegger commented on OAK-6346:

Can you please add more explicit instructions what the steps are when:
- A stable release is cut from a branch. Any changes for the branch the release happened on?
Given the patch you proposed for the documentation, trunk would have to be updated if the
stable release was done from the most recent branch.
- An unstable release is cut. Any updates required?
- A branch is created in preparation for a new stable minor 1.x.0 or major x.0.0 release.
What changes are needed in trunk and the newly created branch?

Not sure if above list is complete...

> Set baseline plugin comparison version to 1.6.0
> -----------------------------------------------
>                 Key: OAK-6346
>                 URL: https://issues.apache.org/jira/browse/OAK-6346
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: parent
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.8
>         Attachments: OAK-6346-v1.patch, release-process-v1.patch
> The purpose of baseline plugin is to ensure that any change in api get reflected in exported
version of the package. Currently the baseline plugin compares against the immediate previous
> This causes issue with unstable branches where new features are being implemented and
which evolve over few minor release on the trunk. In such cases its possible that a new method
expose in 1.7.1 gets removed later in 1.7.2 (as happened in OAK-6337).
> It would be better to configure baseline plugin to check against releases from stable
branch so that we can ensure that package versions are properly aligned against stable versions

This message was sent by Atlassian JIRA

View raw message