|
15 | 15 | </developer> |
16 | 16 |
|
17 | 17 | <!-- Requered: Should be a link to the upstream homepage for the component --> |
18 | | - <url type="homepage">https://example.org/</url> |
| 18 | + <url type="homepage">https://github.com/ranfdev/DistroShelf</url> |
19 | 19 | <!-- Recommended: It is highly recommended for open-source projects to display the source code repository --> |
20 | | - <url type="vcs-browser">https://example.org/repository</url> |
| 20 | + <url type="vcs-browser">https://github.com/ranfdev/DistroShelf</url> |
21 | 21 | <!-- Should point to the software's bug tracking system, for users to report new bugs --> |
22 | | - <url type="bugtracker">https://example.org/issues</url> |
| 22 | + <url type="bugtracker">https://github.com/ranfdev/DistroShelf/issues</url> |
23 | 23 | <!-- Should link a FAQ page for this software, to answer some of the most-asked questions in detail --> |
24 | 24 | <!-- URLs of this type should point to a webpage where users can submit or modify translations of the upstream project --> |
25 | | - <url type="translate">https://example.org/translate</url> |
26 | | - <url type="faq">https://example.org/faq</url> |
| 25 | + <!-- <url type="translate">https://example.org/translate</url> --> |
| 26 | + <!-- <url type="faq">https://example.org/faq</url> --> |
27 | 27 | <!--Sould provide a web link to an online user's reference, a software manual or help page --> |
28 | | - <url type="help">https://example.org/help</url> |
| 28 | + <!-- <url type="help">https://example.org/help</url> --> |
29 | 29 | <!-- URLs of this type should point to a webpage showing information on how to donate to the described software project --> |
30 | | - <url type="donation">https://example.org/donate</url> |
| 30 | + <url type="donation">https://github.com/sponsors/ranfdev</url> |
31 | 31 | <!--This could for example be an HTTPS URL to an online form or a page describing how to contact the developer --> |
32 | | - <url type="contact">https://example.org/contact</url> |
| 32 | + <!-- <url type="contact">https://example.org/contact</url> --> |
33 | 33 | <!--URLs of this type should point to a webpage showing information on how to contribute to the described software project --> |
34 | | - <url type="contribute">https://example.org/contribute</url> |
| 34 | + <!-- <url type="contribute">https://example.org/contribute</url> --> |
35 | 35 |
|
36 | 36 | <translation type="gettext">distroshelf</translation> |
37 | 37 | <!-- All graphical applications having a desktop file must have this tag in the MetaInfo. |
|
59 | 59 | </screenshots> |
60 | 60 |
|
61 | 61 | <releases> |
62 | | - <release version="1.0.1" date="2024-01-18"> |
63 | | - <url type="details">https://example.org/changelog.html#version_1.0.1</url> |
| 62 | + <release version="1.0.1" date="2025-03-25"> |
64 | 63 | <description translate="no"> |
65 | | - <p>Release description</p> |
| 64 | + <p>First release</p> |
66 | 65 | <ul> |
67 | | - <li>List of changes</li> |
68 | | - <li>List of changes</li> |
| 66 | + <li>Create and manage containers</li> |
| 67 | + <li>View container status and details</li> |
| 68 | + <li>Install packages</li> |
| 69 | + <li>Manage exported applications</li> |
| 70 | + <li>Open terminal sessions</li> |
| 71 | + <li>Upgrade containers</li> |
| 72 | + <li>Clone and delete containers</li> |
69 | 73 | </ul> |
70 | 74 | </description> |
71 | 75 | </release> |
|
0 commit comments