From 56fd9646fc9fc6b1e759a7d13bb84ca972679e46 Mon Sep 17 00:00:00 2001 From: Jehan Date: Wed, 27 Dec 2017 20:03:49 +0100 Subject: [PATCH 1/3] docs: minor fix of repeated word. s/The the/The/ --- docs/sources/metainfo/component.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/metainfo/component.xml b/docs/sources/metainfo/component.xml index c573b856..79d9612f 100644 --- a/docs/sources/metainfo/component.xml +++ b/docs/sources/metainfo/component.xml @@ -368,7 +368,7 @@ The date property can have any time in ISO 8601 format as its value and should be present for every release. The timestamp tag contains the release time in the form of a UNIX epoch. This tag should not be used in metainfo files in newly - written metadata, but will still be parsed in case it is present. The the timestamp property is mainly used in generated distro-metadata. + written metadata, but will still be parsed in case it is present. The timestamp property is mainly used in generated distro-metadata. In case both release-time tags are present, the timestamp tag will take precedence over date. From ae32358d87a6f08a7b6b60b2bdbfea1c4bf649f1 Mon Sep 17 00:00:00 2001 From: Jehan Date: Wed, 27 Dec 2017 20:36:44 +0100 Subject: [PATCH 2/3] docs: the listing of should have a "type" property. To differentiate from dev or stable releases in particular. --- docs/sources/metainfo/component.xml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/sources/metainfo/component.xml b/docs/sources/metainfo/component.xml index 79d9612f..926c59b5 100644 --- a/docs/sources/metainfo/component.xml +++ b/docs/sources/metainfo/component.xml @@ -386,6 +386,22 @@ If no urgency is defined, a medium urgency is implicitly assumed. The urgency defines how the update will be presented to the user, and sometimes if it will be installed automatically and immediately, or delayed. + + Finally a release tag may have a type property + to classify releases with one of the following values: + + + stable + development + RC + + + By default, if no release type is defined, stable is assumed. + A software displaying a listing of releases should only show stable releases and + discard any development or release candidate releases if the current version is + itself stable. It can show all versions when development or release candidates are + also distributed. + Each release tag may have a description tag as child, containing a brief description of what is new in the release. The description tag is structured as described in . @@ -405,6 +421,7 @@ 12345678 42424242 + ]]> From 62a9a30ad19605939b54663ddff68a366a35bd4c Mon Sep 17 00:00:00 2001 From: Jehan Date: Thu, 28 Dec 2017 16:51:11 +0100 Subject: [PATCH 3/3] docs: type can be only one of "stable" and "development". As per bug report discussion. --- docs/sources/metainfo/component.xml | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/sources/metainfo/component.xml b/docs/sources/metainfo/component.xml index 926c59b5..caee3bbd 100644 --- a/docs/sources/metainfo/component.xml +++ b/docs/sources/metainfo/component.xml @@ -393,14 +393,12 @@ stable development - RC By default, if no release type is defined, stable is assumed. A software displaying a listing of releases should only show stable releases and - discard any development or release candidate releases if the current version is - itself stable. It can show all versions when development or release candidates are - also distributed. + discard any development release if the current version is itself stable. It can + show all versions when development versions of the software are also distributed. Each release tag may have a description tag as child, containing a brief description of what is new in the release.