Github user davidyan74 commented on a diff in the pull request:
https://github.com/apache/incubator-apex-site/pull/19#discussion_r56070632
--- 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.
+
+The type of change will inform the required target version number. Given a
version number MAJOR.MINOR.PATCH, increment the:
+
+* MAJOR version when you make incompatible API changes,
+* MINOR version when you add functionality in a backwards-compatible
manner, and
+* PATCH version when you make backwards-compatible bug fixes.
--- End diff --
I think we don't need the "s" in backward-compatible
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
