|
VersionPolicy
SabreDAV versioning policy
VersioningSabreDAV is now considered stable (and 1.0 at the time of writing). SabreDAV features are split in the following 2 major pieces: End-user APIThe End-user API is the api that consists of the following classes:
No backwards compatible changes will be made to these classes until version 2.0 of SabreDAV. Plugin APIThe Plugin API is relates to:
The plugin API is constantly evolving. This is largly due to the necessary changes required by implementing RFC 3744 (ACL support). Because very little people will likely write plugins on their own, and most people will just use the End-user API, some flexibility is required here. Therefore no backwards compatibile changes will be made in 1.0.* versions of SabreDAV. Beta and Alpha versionsOdd-numbers in the minor version are reserved for beta and alpha-releases only. This means that the 1.1.* range will solely be dedicated for new beta and alpha versions. When features developed within the 1.1 branch reach stability, these changes will be rolled into a new 1.2 release. 1.0.*, 1.2.* are really reserved for bugfixes-only. PHP / other dependency breaksCurrently the minimum required version for SabreDAV is 5.2. In the future SabreDAV might require 5.3 for certain new features. This might be done in a minor revision change, such as 1.2. If, in the future a switch from PEAR-style packages to PHP namespaces is made, this means the end-user API will break and thus can only roll into a 2.0 (or 3.0) release. |
Sign in to add a comment