Someone proposes us (GIMP) to use the appdata <release> tags instead of NEWS (and actually even to generate NEWS from these <release> appdata).
As we start using <release>, this makes sense since that is a bit duplicate info, especially since now we can add a "type" to a release tag (cf. #158, thanks for this!).
Yet I wonder how detailed you expect the <release> data to be. Our NEWS file is pretty detailed (this can be considered as the most exhaustive human readable text for new features of a release; if you want more detailed basically you look at the git log): https://git.gnome.org/browse/gimp/tree/NEWS
I may be wrong, but I feel that you don't expect the <release> tags to be this detailed. Since this is used as release information in a software installer, I assumed you expect more a concise text only featuring the biggest changes.
For instance, here is the text I started to write for our 2.10 release: https://git.gnome.org/browse/gimp/tree/desktop/org.gimp.GIMP.appdata.xml.in.in#n73
As you can see, just a few major points (this is like 50 times smaller than even each intermediary release in NEWS).
Could you tell us what you think? Does it make sense to have extra-detailed <release> tags, in which case, we would merge the NEWS concept into appdata (NEWS may just become a generated file)? Or should the appdata just be a summarized and succinct version of NEWS, telling of a release in a few points?
The text was updated successfully, but these errors were encountered:
Hi!
Someone proposes us (GIMP) to use the appdata
<release>tags instead of NEWS (and actually even to generate NEWS from these<release>appdata).As we start using
<release>, this makes sense since that is a bit duplicate info, especially since now we can add a "type" to a release tag (cf. #158, thanks for this!).Yet I wonder how detailed you expect the
<release>data to be. Our NEWS file is pretty detailed (this can be considered as the most exhaustive human readable text for new features of a release; if you want more detailed basically you look at the git log): https://git.gnome.org/browse/gimp/tree/NEWSI may be wrong, but I feel that you don't expect the
<release>tags to be this detailed. Since this is used as release information in a software installer, I assumed you expect more a concise text only featuring the biggest changes.For instance, here is the text I started to write for our 2.10 release: https://git.gnome.org/browse/gimp/tree/desktop/org.gimp.GIMP.appdata.xml.in.in#n73
As you can see, just a few major points (this is like 50 times smaller than even each intermediary release in NEWS).
Could you tell us what you think? Does it make sense to have extra-detailed
<release>tags, in which case, we would merge the NEWS concept into appdata (NEWS may just become a generated file)? Or should the appdata just be a summarized and succinct version of NEWS, telling of a release in a few points?The text was updated successfully, but these errors were encountered: