[lsc-changes] [Ldap Synchronization...] page changed: qa:releasepolicy

[webmaster]

A page in your DokuWiki was added or changed. Here are the details:

Date : 2014/03/06 15:43
Browser : Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0
IP-Address : 88.173.78.196
Hostname : mne69-10-88-173-78-196.fbx.proxad.net
Old Revision: http://lsc-project.org/wiki/qa/releasepolicy?rev=1325801135
New Revision: http://lsc-project.org/wiki/qa/releasepolicy
Edit Summary:
User : coudot

@@ -4,9 +4,9 @@

LSC versions numbers contain 3 components: **X.Y.Z**.

- An increment in **Z** is referred to as a minor update (example: 1.1.0 to 1.1.1).
- - An increment in **Y** is referred to as a major update (example: 1.1.1 to 1.2.0) which had new features but does not brake the ascending compatibility.
+ - An increment in **Y** is referred to as a major update (example: 1.1.1 to 1.2.0) which had new features but does not brake the ascending compatibility. It implies configuration modification to use the new XML schema.
- An increment in **X** is referred to as a brand new version (ex 1.2.1 to 2.0) which implies a new design, gains many new features but requires a requalification of the deployed instances.

===== Minor updates =====

@@ -18,6 +18,8 @@

Major updates introduce new functionality. Schedules depend on when features are implemented, not on a specific date. The [[http://tools.lsc-project.org/roadmap|Roadmap]] offers more detailed information about these.

Backward-compatibility of major releases is generally available up to release Y-2. For example, migrating from 1.1.Z to 1.2.0 will be transparent. However, in version 1.3.Z may drop compatibility with some 1.1.Z features.
+
+ As the configuration file is in XML, and validated with an XSD file, switching to a new major release implies to update the XML namespace definition of all configuration files.

In all cases, any non backward-compatible changes will be documented in detail in the release notes.