You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by "Chandni Singh (JIRA)" <ji...@apache.org> on 2016/02/22 21:26:18 UTC

[jira] [Created] (APEXCORE-351) Exclude classes marked as Evolving/Unstable from semver check

Chandni Singh created APEXCORE-351:
--------------------------------------

             Summary: 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)