Metadata: Add missing entries
The current metadata of Calendar look like this on Gnome Software (for Flathub repo):
However the current Appstream specification allows for more information displayed, giving this result for example:
I suggest updating Calendar metadata to add such information.
Moreover, the information about releases for Calendar exists in two separate places:
- https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/main/NEWS
- https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/main/data/appdata/org.gnome.Calendar.appdata.xml.in.in
They do not contain the same information about releases. It is also possible to tag releases as stable or development:
"A release tag may have a type property to classify releases with one of the following values:
- stable
- development
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 release if the current version is itself stable. It can show all versions when development versions of the software are also distributed."
Might be interesting to use that so that the Gnome Software center doesn't display development releases. It would give a purpose to the two places containing release info:
- News could contain new features between each release (stable and development);
- Metadata could only contain information about stable releases. (and maybe have some information for development releases that are not relevant to the end user.)
Also the Appstream specification says:
"While desktop-application metadata is commonly stored in /usr/share/metainfo/%{id}.metainfo.xml (with a .metainfo.xml extension), using a .appdata.xml extension is also permitted for this component type for legacy compatibility. AppStream implementations will recognize either file type, as long as it ends up in the right location on the filesystem."
It might be interesting to rename the Calendar metadata file to be more "up to date" but it is not needed, let me know what you think about this.
This is a lot of information and it could be nice to break this issue into multiple ones. Once there is more feedback about this issue I will propose an appropriate fix.