apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Weise (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (APEXCORE-351) Exclude classes marked as Evolving/Unstable from semver check
Date Thu, 25 Feb 2016 06:14:18 GMT

     [ https://issues.apache.org/jira/browse/APEXCORE-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Weise closed APEXCORE-351.
---------------------------------
    Resolution: Duplicate

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

Mime
View raw message