[
https://issues.apache.org/jira/browse/APEXCORE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194067#comment-15194067
]
ASF GitHub Bot commented on APEXCORE-319:
-----------------------------------------
Github user davidyan74 commented on a diff in the pull request:
https://github.com/apache/incubator-apex-site/pull/19#discussion_r56069972
--- Diff: src/md/compatibility.md ---
@@ -0,0 +1,112 @@
+#Apache Apex Compatibility
+
+##Purpose
+
+This document captures the compatibility goals of the Apache Apex project.
The different types of compatibility between Apex releases that affect
contributors, downstream projects, and end-users are enumerated. For each type
of compatibility we:
+
+* describe the impact on downstream projects or end-users
+* where applicable, call out the policy adopted when incompatible changes
are permitted.
+
+Apache Apex follows [semantic versioning](http://semver.org/). Depending
in the compatibility type, there may be different tools or mechanisms to ensure
compatibility, for example by comparing artifacts during the build process.
--- End diff --
Depending "on"?
> Document backward compatibility guidelines
> ------------------------------------------
>
> Key: APEXCORE-319
> URL: https://issues.apache.org/jira/browse/APEXCORE-319
> Project: Apache Apex Core
> Issue Type: Task
> Reporter: Chris Nauroth
> Assignee: Thomas Weise
> Labels: tlp
>
> QU40
> The project puts a high priority on backwards compatibility and aims to
> document any incompatible changes and provide tools and documentation to help
> users transition to new features.
> I couldn't find backwards-compatibility guidelines documented at
> apex.incubator.apache.org. Example:
> http://hadoop.apache.org/docs/r2.7.2/hadoop-project-dist/hadoop-common/Comp
> atibility.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
