Merge #7006: chore: add flatpak metainfo

d978ba7 refactor: dedicated content_attribute tag inside content_rating (PastaPastaPasta)
117ce7e docs: release data -> date (PastaPastaPasta)
f38b088 fix: proper date, trailing space (pasta)
fbe1544 docs: add flatpak metainfo to release process (pasta)
cdeb056 chore: add v23 release to flatpak metainfo (pasta)
dcf846a fix: improper order of releases (Pasta)
81d7511 chore: bump org.dash.dash-core.metainfo.xml for v22.0.0 (Pasta)
5f63710 fix: content_attribute does not exist, include in content_rating (fanquake)
9835031 chore: add money-purchasing attribute to .xml in response flatpak discussion (pasta)
7fa5660 chore: add metainfo.xml for flatpak / flathub (pasta)

Pull request description:

  ## Issue being fixed or feature implemented
  Merge (a rebased version of) feat/flatpak into develop

  adds contrib/flatpak/org.dash.dash-core.metainfo.xml and updates release process with related reminder.

  This doesn't need to be back ported; having it in develop is fine.

  ## What was done?
  We have to update this file so that: https://flathub.org/en/apps/org.dash.dash-core reports correct version info

  ## How Has This Been Tested?

  ## Breaking Changes

  ## Checklist:
    _Go over all the following points, and put an `x` in all the boxes that apply._
  - [ ] I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [ ] I have made corresponding changes to the documentation
  - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_

ACKs for top commit:
  UdjinM6:
    utACK d978ba7

Tree-SHA512: 368b5882ad9d19c433184c303c1a191c3eb3efe16eaf40fda88184f8a387d9e5cad5dc9a5830e122e611c0b6b7a521a6c65937219db9a6b1858603f19f6b0726

Author: PastaPastaPasta

contrib/flatpak/org.dash.dash-core.metainfo.xml

@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<component type="desktop-application">
+  <id>org.dash.dash-core</id>
+  <name>Dash Core</name>
+  <project_license>MIT</project_license>
+  <metadata_license>CC0-1.0</metadata_license>
+  <summary>Fully validating Dash peer-to-peer network node, wallet and GUI</summary>
+  <url type="homepage">https://dash.org/</url>
+  <url type="bugtracker">https://github.com/dashpay/dash/issues/new?title=[flatpak]</url>
+  <launchable type="desktop-id">org.dash.dash-core.desktop</launchable>
+  <description>
+    <p>
+    Dash Core connects to the Dash peer-to-peer network to download and
+    fully validate blocks and transactions. It also includes a wallet and
+    graphical user interface.
+    </p>
+  </description>
+  <screenshots>
+    <screenshot type="default">
+      <image type="source">https://docs.dash.org/en/stable/_images/overview.png</image>
+    </screenshot>
+  </screenshots>
+  <releases>
+    <release date="2025-11-10" version="23.0.0"/>
+    <release date="2024-12-12" version="22.0.0"/>
+    <release date="2024-10-22" version="21.1.1"/>
+  </releases>
+  <content_rating type="oars-1.1">
+    <content_attribute id="money-purchasing">intense</content_attribute>
+  </content_rating>
+  <developer id="org.dash">
+    <name>Dash Core Group</name>
+  </developer>
+</component>

doc/release-process.md

@@ -11,6 +11,7 @@ Before every minor and major release:
 * [ ] Update DIPs with any changes introduced by this release (see [this pull request](https://github.com/dashpay/dips/pull/142) for an example)
 * [ ] Update version in `configure.ac` (don't forget to set `CLIENT_VERSION_IS_RELEASE` to `true`)
 * [ ] Write release notes (see below). To clear the release notes: `cp doc/release-notes-empty-template.md doc/release-notes.md`
+* [ ] Update flatpak [metainfo file](contrib/flatpak/org.dash.dash-core.metainfo.xml) with latest release tag and estimated release date
 * [ ] Update `src/chainparams.cpp` `nMinimumChainWork` with information from the `getblockchaininfo` rpc.
 * [ ] Update `src/chainparams.cpp` `defaultAssumeValid` with information from the `getblockhash` rpc.
   - The selected value must not be orphaned so it may be useful to set the value two blocks back from the tip.