[jira] [Commented] (JCR-4147) clirr profile needs to use sensible baselines
[ https://issues.apache.org/jira/browse/JCR-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058993#comment-16058993 ] Julian Reschke commented on JCR-4147: - bq. I would prefer using the baseline plugin. Right - any objections to disable clirr once baseline is used? > 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)
[jira] [Commented] (JCR-4147) clirr profile needs to use sensible baselines
[ https://issues.apache.org/jira/browse/JCR-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057379#comment-16057379 ] Marcel Reutegger commented on JCR-4147: --- I would prefer using the baseline plugin. It understands semantic versioning and would bring Jackrabbit into line with Oak where the baseline plugin is in use for a while now. Using different tools is in my view confusing and difficult to maintain. > 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)
[jira] [Commented] (JCR-4147) clirr profile needs to use sensible baselines
[ https://issues.apache.org/jira/browse/JCR-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049274#comment-16049274 ] angela commented on JCR-4147: - [~reschke], i only learned about the clirr profile yesterday... looking at http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/security/package-info.java?view=log it seems that i don't have amnesia it really was never updated since Jukka introduced it 5 years ago... all the API extensions we added got "unnoticed" from a export version pov. +1 for both suggestions. > 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)
[jira] [Commented] (JCR-4147) clirr profile needs to use sensible baselines
[ https://issues.apache.org/jira/browse/JCR-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049109#comment-16049109 ] Davide Giannella commented on JCR-4147: --- +1 for latest stable release. Even though it depends on for how long we want to keep compatibility. We *may* have to be compatible to something earlier than 2.14.0 depending purely on arbitrary team decision. +1 for moving this to baseline for trunk (2.15.x) > 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)
[jira] [Commented] (JCR-4147) clirr profile needs to use sensible baselines
[ https://issues.apache.org/jira/browse/JCR-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (JCR-4147) clirr profile needs to use sensible baselines
[ https://issues.apache.org/jira/browse/JCR-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049071#comment-16049071 ] Julian Reschke commented on JCR-4147: - trunk: [r1798666|http://svn.apache.org/r1798666] > 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)
[jira] [Commented] (JCR-4147) clirr profile needs to use sensible baselines
[ https://issues.apache.org/jira/browse/JCR-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049064#comment-16049064 ] Julian Reschke commented on JCR-4147: - [~mreutegg], [~anchela], [~edivad] - feedback appreciated - also, should we move over to baseline? I assume the reason why we use clirr here is entirely historic? > 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 > > 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)
