From 7f97e31e24180c4186725a105b7004515e5ea108 Mon Sep 17 00:00:00 2001 From: David Robillard Date: Sat, 5 Mar 2011 23:58:08 +0000 Subject: Apply "odd number = development version" rule to both version numbers. --- core.lv2/lv2.ttl | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/core.lv2/lv2.ttl b/core.lv2/lv2.ttl index 3011dd1..d95a29a 100644 --- a/core.lv2/lv2.ttl +++ b/core.lv2/lv2.ttl @@ -391,6 +391,13 @@ only be meaningful for a particular plugin instance at run-time).

When hosts discover several installed versions of a resource, they SHOULD warn the user and load only the most recent version.

+

An odd minor or micro version indicates that the resource is a +possibly unstable development version. Hosts and tools SHOULD clearly indicate +this wherever appropriate. Several versions of a resource with an odd version +may exist; i.e. it is acceptable to work on a development version of a resource +(e.g. in source control) without worrying about version numbers as long as +either the minor or micro version is odd.

+

This property describes half of a resource version. See also lv2:minorVersion, the property which describes the other half.

@@ -403,13 +410,6 @@ lv2:microVersion a rdf:Property ; lv2:documentation """

The micro component of a Resource's version.

-

An odd micro version indicates that the resource is a possibly unstable -development version. Hosts and tools SHOULD clearly indicate this wherever it -makes to do so. Several versions of a resource with an odd micro version may -exist globally; i.e. it is acceptable to work on a development version of a -resource (e.g. in source control) without worrying about version numbers as -long as the micro version is odd.

-

Correct version numbers MUST always be maintained for published resources. For example, after a release, if a change is made in the development version in source control, the micro version MUST be incremented (to an odd -- cgit v1.2.1