[
https://issues.apache.org/jira/browse/OAK-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077860#comment-16077860
]
Chetan Mehrotra commented on OAK-6346:
--------------------------------------
Done the changes in trunk with 1801134
bq. It may also be good to update our release documentation and introduce a
step when a new branch is created. That would be the time when trunk needs to
bump the comparison version, right?
Opened OAK-6433 to track that work. Also we may need to bump the version in
oak-parent for next minor releases from 1.6 branch if any change backported
introduces a new api
Would now update the release process
> 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
>
>
> 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)
