Differences between revisions 1 and 2
Revision 1 as of 2012-04-06 18:21:48
Size: 628
Editor: brianleroux
Comment:
Revision 2 as of 2012-04-06 18:22:03
Size: 631
Editor: brianleroux
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
1. All public API method signatures will remain available between MAJOR releases. A signature is considered public if it is documented in the Cordova docs.
2. All JS signatures that are slated for deprecation will have deprecation notices added via console.log to give developers sufficient warning.
3. All native signatures will have analogue shims to maintain backward compatibility. It is recommended, if possible, these shims exist in discreet files and have a companion JIRA ticket assigned to the next MAJOR release for removal.
 1. All public API method signatures will remain available between MAJOR releases. A signature is considered public if it is documented in the Cordova docs.
 2. All JS signatures that are slated for deprecation will have deprecation notices added via console.log to give developers sufficient warning.
 3. All native signatures will have analogue shims to maintain backward compatibility. It is recommended, if possible, these shims exist in discreet files and have a companion JIRA ticket assigned to the next MAJOR release for removal.

Deprecation Policy

Apache Cordova follows a MAJOR.MINOR.PATCH version schema.

  1. All public API method signatures will remain available between MAJOR releases. A signature is considered public if it is documented in the Cordova docs.
  2. All JS signatures that are slated for deprecation will have deprecation notices added via console.log to give developers sufficient warning.
  3. All native signatures will have analogue shims to maintain backward compatibility. It is recommended, if possible, these shims exist in discreet files and have a companion JIRA ticket assigned to the next MAJOR release for removal.