[
https://issues.apache.org/jira/browse/APEXCORE-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157714#comment-15157714
]
ASF GitHub Bot commented on APEXCORE-351:
-----------------------------------------
GitHub user chandnisingh opened a pull request:
https://github.com/apache/incubator-apex-core/pull/233
APEXCORE-351 ignore Unstable/Evolving classes from semver
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chandnisingh/incubator-apex-core APEXCORE-351
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-apex-core/pull/233.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #233
----
commit ad2ee4e211f4ec225c6a48fb70dc5ec0d3f1d9a5
Author: Chandni Singh <[email protected]>
Date: 2016-02-22T21:21:38Z
APEXCORE-351 ignore Unstable/Evolving classes from semver
----
> 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)
