Bugzilla

Status update:
* we were able to succesfully build flatpaks and publish them to the `beta` channel
* we will continue to do so as part of the beta train of 75.0
* for any conversations regarding flatpak manifest improvement that were happening in bug 1621083, let's use bug 1621083 instead

In order to test the currently-shipped Firefox Flatpaks on the Flathub's beta channel:
* depending on the distribution, opening https://flathub.org/beta-repo/appstream/org.mozilla.firefox.flatpakref from browser should cause GNOME Software/KDE discover to ask if user wants to install it
* alternatively `flatpak install --user https://flathub.org/beta-repo/appstream/org.mozilla.firefox.flatpakref`

We still have a couple of issues to solve, like l10n and better building configuration, before we're ready to publish to `stable` channel (and be available via the Flathub UI).

Last but not least, there is a dedicated `Release Automation: Flatpak` component now, within RelEng product, feel free to file bugs against it.

Status update:
* we were able to succesfully build flatpaks and publish them to the `beta` channel
* we will continue to do so as part of the beta train of 75.0
* for any conversations regarding flatpak manifest improvement that were happening in bug 1591387, let's use bug 1621083 instead

In order to test the currently-shipped Firefox Flatpaks on the Flathub's beta channel:
* depending on the distribution, opening https://flathub.org/beta-repo/appstream/org.mozilla.firefox.flatpakref from browser should cause GNOME Software/KDE discover to ask if user wants to install it
* alternatively `flatpak install --user https://flathub.org/beta-repo/appstream/org.mozilla.firefox.flatpakref`

We still have a couple of issues to solve, like l10n and better building configuration, before we're ready to publish to `stable` channel (and be available via the Flathub UI).

Last but not least, there is a dedicated `Release Automation: Flatpak` component now, within RelEng product, feel free to file bugs against it.