[
https://issues.apache.org/jira/browse/OAK-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507913#comment-16507913
]
Julian Reschke commented on OAK-6346:
-------------------------------------
{quote} in trunk, we should specify the last stable release
I would rather not do this. Releases off a branch should not introduce changes
that require a package export version bump. If this is allowed a package can
diverge and still export the same version.{quote}
If the release branch does indeed never changes the export version, then
there's no problem, and referring to the latest stable release is the same as
referring to the first (here 1.8.0). *If* the release branch however changes
for some reason, we absolutely have to take this into account for the trunk
baseline check, no?
> 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
> Priority: Major
> Fix For: 1.10
>
> 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
(v7.6.3#76005)
