[
https://issues.apache.org/jira/browse/APEXCORE-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166494#comment-15166494
]
ASF GitHub Bot commented on APEXCORE-351:
-----------------------------------------
Github user vrozov commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/233#issuecomment-188546101
It is fixed now in the PR along with the version change.
> Exclude classes marked as Evolving/Unstable from semver check
> -------------------------------------------------------------
>
> Key: APEXCORE-351
> URL: https://issues.apache.org/jira/browse/APEXCORE-351
> Project: Apache Apex Core
> Issue Type: Improvement
> Reporter: Chandni Singh
> Assignee: Chandni Singh
>
> As we add new features, new APIs or common implementations of existing ones
> maybe added. However there maybe a need to change these classes sooner with
> minor version updates as they are new and can only become stable with usage.
> In order to facilitate backward incompatible changes with minor version
> updates, we can flag interfaces/classes as Unstable/Evolving and so they can
> be skipped by semantic versioning.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
