Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Propose a "type" property to <release/> tag. #158

Merged
merged 3 commits into from Jan 24, 2018
+16 −1
Merged

Propose a "type" property to <release/> tag. #158

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
56fd964
docs: minor fix of repeated word.
Dec 27, 2017
ae32358
docs: the listing of <release> should have a "type" property.
Dec 27, 2017
62a9a30
docs: <release> type can be only one of "stable" and "development".
Dec 28, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
17 docs/sources/metainfo/component.xml
View file
Open in desktop
@@ -368,7 +368,7 @@
The <literal>date</literal> property can have any time in <ulink url="https://en.wikipedia.org/wiki/ISO_8601">ISO 8601</ulink> format as its value and
should be present for every release.
The <literal>timestamp</literal> 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 <literal>timestamp</literal> property is mainly used in generated distro-metadata.
written metadata, but will still be parsed in case it is present. The <literal>timestamp</literal> property is mainly used in generated distro-metadata.
In case both release-time tags are present, the <literal>timestamp</literal> tag will take precedence over <literal>date</literal>.
</para>
<para>
@@ -386,6 +386,20 @@
If no urgency is defined, a <code>medium</code> 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.
</para>
<para>
Finally a <literal>release</literal> tag may have a <literal>type</literal> property
to classify releases with one of the following values:
</para>
<itemizedlist>
<listitem><para><literal>stable</literal></para></listitem>
<listitem><para><literal>development</literal></para></listitem>
</itemizedlist>
<para>
By default, if no release type is defined, <code>stable</code> is assumed.
A software displaying a listing of releases should only show stable releases and
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.
</para>
<para>
Each <literal>release</literal> tag may have a <literal>description</literal> tag as child, containing a brief description of what is new in the release.
The <literal>description</literal> tag is structured as described in <xref linkend="tag-description"/>.
@@ -405,6 +419,7 @@
<size type="download">12345678</size>
<size type="installed">42424242</size>
</release>
<release version="1.1" type="development" date="2013-10-20" />
<release version="1.0" date="2012-08-26" />
</releases>]]></programlisting>
</listitem>