You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/07/07 09:46:00 UTC

[jira] [Updated] (OAK-6346) Set baseline plugin comparison version to 1.6.0

     [ https://issues.apache.org/jira/browse/OAK-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra updated OAK-6346:
---------------------------------
    Attachment: release-process-v1.patch

[patch|^release-process-v1.patch] for the release process

[~edivad] [~mreutegg] Please review

> 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 version. 
> 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
(v6.4.14#64029)