Should there be an Advisory announcement on 6.0 - 6.0.1?

Development Bug triage
1

There are discovered significant issues that are still without patches. Since the conversion to 6.0.x from 5.x is “one way”, should users be advised to pause in upgrading?

  • the orjson dependency is not bundled in all Linux distributions. And a simple (for novice, not programmer Linux users) manual install workflow has not been promoted.
  • The custom filter optimizer difficulties are still being isolated and resolved
2

Also, the 6.0 Addon Manager NOT recognizing that a mismatch occurs with 5.2 addon-__.json URLs and 5.2 target versioned addons impacted certain communities heavily.

Some users of Experimental addons and the Isotammi-using Finnish community have had their confidence in 6.0. shaken.

3

I agree, the distribution of version 6 should be hauled until these important issues are resolved.

4

As a bystander in all this (sticking with 5.2.4. until at least Spring
of next year) and a Debian user LMDE 6 and Raspberry Pi I have briefly
tried GRAMPS 6 found nothing I desperately needed from a family history
perspective and uninstalled until Debian Trixie is released.
Looking at the issues raised I would suspect that it should at least
have a clear Warning of Experimental not for anyone other than the very
experienced user/developer.
phil

5

As a Gramps user for over 10 years, I sympathise. I use Xubuntu and always go for the LTS versions for relative ‘stability’ (24.04 LTS for now)

I’ve read some of the posts regarding the problems users are having with package dependencies. I’ve tried to understand building from source too. So far I have not found way to upgrade to v6 so I am staying where I am for now - sorry.
.

6

I also sympathize. I have upgraded to 6.0.0, but it was somewhat
painful, and so far I haven’t seen changes from 5.2 that matter to me.
I am using Kubuntu (recently upgraded to 25.04) and I was able to use
the Debian package to install 6.0.0. I attempted to install 6.0.1 from
source, but too many things have changed since I last did any serious
development in Python and I realized I was going to have to do a lot
more work than I wanted to do right now, so I will wait for a Debian
package for 6.0.1 if I switch at all.

As it turned out, the most painful part of the upgrade was due to files
being moved from ~/.gramps in older versions to ~/.config/gramps and
~/.local/share/gramps for Gramps 6.0. Once I learned that I was able to
get it working and I haven’t encountered any bugs so far. I’m going to
have to spend some time looking at the Narrative Web report generated by
6.0.0 as it is somewhat different, but at least I didn’t have to make
any changes to the code to get it to work.