Comment 41 for bug 1813441

Vlad, honestly, I don't see this getting fixed anytime soon, this has
been an issue since a late revision of 18.10/19.04 (~2018).

Pinning is a time-tested solution for regressions but it does come with
overhead, especially when the issue is actually a dependency of a core
system component (nautilus).

It would have been better if Canonical could have gotten in front of the
issue when it was first fresh (before the broken expectations). Its
always better to under-promise expectations than to over-promise. At
this point, not meeting expectations, and the failure to act has people
looking for alternatives (myself included).

At this point I don't think the feedback canonical is getting regarding
changes is working in a way that can let them do better.

N.

On 3/13/21 9:34 AM, Jonathan Kamens wrote:

> Claiming that Ubuntu could simply have stuck with the previous version
> of GNOME when shipping the LTS release is failing to see the forest for
> the trees. Many factors go into the decision of what version of a
> critical package like GNOME to put in a release. Ubuntu looked at all of
> those factors and made the decision they did. Unless you were involved
> in that discussion or have done an analysis similar to theirs, you are
> in no position to second-guess their decision; you simply are not
> considering even a small fraction of the information they considered
> when making it.
>
> Desktop Icons NG was around when 20.04 shipped, though it probably
> wasn't complete, tested, or stable enough to ship with an LTS release.
> There have been significant changes since 20.04 shipped.
>