Hi, Alessio

On 1/19/22 12:47, Alessio wrote:
Hello all.

Continuing this thread
https://lists.gnu.org/archive/html/health/2022-01/msg00015.html

As far as I can understand, the metainfo.xml file shuld include the
<releases> tag, and inside this one, the <release> child tag should be
added for each new version.

Reference:
https://freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-releases

Looking at the documentation, it could seem very complex, but a snippet
like this (for eache version) is sufficient:
> <release version="1.0.6" date="2022-01-XX">
     <description>
         <p>Release of version: 1.0.6</p>
     </description>
     <url>https://pypi.org/project/MyGNUHealth/1.0.6</url>
</release>


This would be a preview of how it would look

    <release version="1.0.6" date="2022-1-20" urgency="low">
      <description>
<p>Release of version: 1.0.6. Update metainfo and desktop files.</p>
      </description>
      <url>https://pypi.org/project/MyGNUHealth/1.0.6</url>
    </release>


Ideally the <url> child tag (not to be confused with
https://freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-url
), should point to a changelog web page.


Yes. We can specify the type of URL. We have a Changelog file in Savabbag that can be used (for example https://hg.savannah.gnu.org/hgweb/health-mygnuhealth/file/bebbbb95317a/Changelog)

I have made some minor updates in the current metainfo file, specially the license (GPLV3 or later) and description. I will also review the current documentation RST files (English and Spanish) for improvements.

https://hg.savannah.gnu.org/hgweb/health-mygnuhealth/rev/0931dd1aec96

Let me know your thoughts

All the best
Luis


Reply via email to