[
https://issues.apache.org/jira/browse/JCR-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049088#comment-16049088
]
Julian Reschke commented on JCR-4147:
-------------------------------------
Ok, after digging further, it seems that clirr can only check compatibility,
not semantic versioning.
Thus:
- release branches should use a clirr baseline of their *.0 version
- trunk doesn't need a clirr check
Does this sound right? It would also mean that we need to introduce baseline
checks to check the versions of exported packages.
> clirr profile needs to use sensible baselines
> ---------------------------------------------
>
> Key: JCR-4147
> URL: https://issues.apache.org/jira/browse/JCR-4147
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-parent
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Labels: candidate_jcr_2_10, candidate_jcr_2_12,
> candidate_jcr_2_14, candidate_jcr_2_4, candidate_jcr_2_6, candidate_jcr_2_8
> Fix For: 2.15.4
>
>
> For the "clirr" profile, we currently use a baseline of Jackrabbit 2.2.0
> throughout. This doesn't make any sense, it should be the previous stable
> release.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
