If you have install flatpak apps to your systems, a lot of the runtime environment will be shared - so that final download will be way less then the estimates given as 2.1GB.
There are pros and cons to choose between the two. Personally, I will use the RPM version unless there is a reason not to: like version, easy of upgrade, bundled libraries, etc.
Not a clue then—pkcon install thunderbird did give me the latest version, so packagekit clearly sees it. I’m no longer confident of how gnome-software gets its metadata etc.
I’m a bit unsure which is the preferable solution, since in my opinion, email is the most vulnerable component of an internet facing computer so I would say that it’s important to not share any environment with the email client.
Can we discuss that further? It’s not absolute clear to me.
It was released on June 1, which is 3 working days ago. let’s give the maintainers time to push updates—remember that they need to build from source and run lots of checks before they push updates to users.
Package maintainers follow upstream development closely and decide what releases are to be pushed to users etc. So I’d just trust them here. It really isn’t necessary that every new release be pushed to users. Sometimes maintainers skip a release if they know another one is on the horizon etc.
If you want to know more about this particular package, best to file a bug so that you can communicate with the maintainers directly (if one is not already filed):
There is another point to think about, when choosing Flatpak or RPM.
For example “Evolution”:
The RPM-Version integrates in your Environment, so that for example, under Gnome the Calendar in the Topbar shows your Entries from your Calendar.
The Flatpak-Version don’t, because it is kind of sandboxed.
Had this “issue” some times with different apps, where the Flatpak-Version couldn’t see the pathes I wanted to see. Surely, there is a way to configure, but I where lazy and installed the rpm-version.
Don’t know, if there is a point in Thunderbird, where this becomes interesting.
Depends on the severity of the issues I guess. Best to discuss it with the maintainers—I don’t use/maintain this particular package so I’m speaking in general terms here.