1. 28 May, 2018 1 commit
  2. 25 May, 2018 1 commit
  3. 20 May, 2018 4 commits
  4. 13 May, 2018 2 commits
  5. 11 May, 2018 1 commit
  6. 28 Apr, 2018 2 commits
  7. 27 Apr, 2018 1 commit
  8. 26 Apr, 2018 1 commit
    • Jehan's avatar
      desktop: use tilde for 'rc' separation in version scheme. · 60578285
      Jehan authored
      In other words, number the release candidates: 2.10.0~rc*.
      In any case, this makes `rpmdev-vercmp` to consider them before 2.10.0,
      unlike using a hyphen separator.
      Though I still leave the <releases> trick from commit fb6328b9 so that
      our unit test succeeds, since `appstream-util` still considers the other
  9. 25 Apr, 2018 2 commits
  10. 24 Apr, 2018 1 commit
  11. 10 Apr, 2018 4 commits
  12. 01 Apr, 2018 1 commit
  13. 30 Mar, 2018 1 commit
  14. 25 Mar, 2018 4 commits
  15. 23 Mar, 2018 1 commit
  16. 17 Mar, 2018 1 commit
  17. 21 Feb, 2018 1 commit
  18. 01 Feb, 2018 4 commits
    • Jehan's avatar
    • Jehan's avatar
      desktop: fix the appstream unit tests. · 5fc91e92
      Jehan authored
      The first validation command was actually failing but the test was not,
      because only the last return value is taken into account, obviously. Add
      a '&&' between the commands.
      Also test against the built files, not the templates (in particular
      because `appstream-util` doesn't like .in.in templates, and anyway it's
      always better to test against the finale file).
      Finally move to "validate-relax" test for the time being.
      "validate-strict" actually makes a bunch of errors, but I can't make the
      time to look at these now. Let's just settle with basic validation at
    • Jehan's avatar
      Bug 779839 - Add <releases>-Tag to the gimp.appdata.xml.in. · 78f251b0
      Jehan authored
      - appstream-util returns a "style-invalid" error: "<ul> cannot start a
        description [(null)]". So I add a <p> introduction to the 2.9.8
        <release> tag. This was part of unit test failure on the appdata file.
      - I also add a type property for 2.9.8. This is a new property which I
        proposed and which just got accepted in the appstream specification:
      - I add <release> tags for all previous 2.9.x releases. No description
        for these, just a type property. But feel free to propose patches
        adding short non-technical description for these.
      Note: it was originally proposed in the bug report to use the appdata
      file in place of NEWS (and have this one generated from appdata). But
      after discussion with appstream project, appdata is expected to be
      concise, non-technical and more "marketing" than exhaustive. This is
      quite a different usage than NEWS which is more an exhaustive summary of
      new features and major changes. So these 2 files will likely remain
    • Nate Graham's avatar
      desktop: added release information to the AppStream file... · 6d26f78c
      Nate Graham authored
      ... pre-populated with release notes from version 2.9.8.
  19. 29 Jan, 2018 1 commit
    • Jehan's avatar
      desktop: minor appdata <release> tag update. · abc1fbde
      Jehan authored
      Please everyone, review the contents of this <release> tag so that we
      can quickly uncomment it and submit it for translation. This is what
      will be featured in software installers. Let's make it a concise yet
      interesting overview of the 2.10 release.
  20. 14 Jan, 2018 3 commits
    • Jehan's avatar
      Rename gimp.appdata.xml.in to org.gimp.GIMP.appdata.xml.in.in. · 458e3130
      Jehan authored
      I completely forgot to rename the appstream file according to the new
      ID. While doing so, I also make it a .in.in file, with initial
      processing by the autotools. Indeed I need @GIMP_COMMAND@ to be replaced
      by AC_CONFIG_FILES().
      Finally I fix a badly closed XML tag (which reminds me I should always
      test a commit, even when it's a simple non-C 1-liner change!).
    • Jehan's avatar
      desktop: update the appdata to take care of the id change. · 54dda25c
      Jehan authored
      From AppStream docs:
      In previous AppStream releases, the <id/> was used to associate metainfo
      files with their .desktop files to merge in data from .desktop files
      into the AppStream generator's final output. In modern metainfo files,
      the component-ID for desktop-application components can be an arbitrary
      string (matching the naming rules applying to all AppStream metadata),
      while the <launchable/> tag is used to associate .desktop files with
      their metainfo files.
    • Nate Graham's avatar
      Bug 791861 - Update appdata.xml AppStream ID to match rDNS-style... · d39f7d6f
      Nate Graham authored
      ... used for Flatpak.
      Additional comments by Jehan after review:
      This is not only to sync with flatpak. This format is the recommended
      format in AppStream spec, even though many historical application still
      use the old format.
      If ever we decide to propose a dbus service, this may even become
      However just changing this is not enough for a proper ID change. I will
      make additional change in further commits.
  21. 27 Dec, 2017 3 commits
    • Jehan's avatar
      desktop: add (commented-out) release tag for 2.10. · a017668b
      Jehan authored
      Let's start from here. I don't think it needs to be too long, just a
      summary of the most awesome changes, I'd say.
      Let's leave it commented out for now, until the description is finished
      and ready for localization. This is the description which may appear in
      software installers using appstream metadata.
    • Jehan's avatar
      desktop: add <release> tags for 2.8.x. · 3595ef9d
      Jehan authored
      Did a bit of archeology to get all the dates back.
      I didn't add any description. Not sure if we should bother that much for
      older versions (but most probably for upcoming version, would be
      I also wanted to add URLs to the various news for each release, but
      appstream-util would fail, telling that hyperlinks are not allowed
      inside <p>. Unfortunately <release> tag cannot have a <url> child (nor a
      property) according to appstream docs. So for now, I'll just stick to
      date listing.
    • Jehan's avatar
      desktop: use HTTPS everywhere. · b9c2c9ac
      Jehan authored
      We now use HTTPS everywhere on the website. The link would be anyway
      redirected, but we may as well write down the good link directly.