Hi, I’m one of the upstream maintainers. Apologies for the confusion on this; Graphviz has indeed gone through a variety of pretty unorthodox versioning schemes.
At present, the situation is much more straightforward: Graphviz follows semantic versioning and adds a Git tag for every release. E.g. the latest release is tagged “2.49.3” There’s no more distinction between stable vs development vs experimental. Every Graphviz release is considered stable. I presume the Debian package is consuming the so-called “portable source” tarball, for which we’ve had a lot of difficulty maintaining stable URLs, as hinted at by prior posts on this bug as well as https://gitlab.com/graphviz/graphviz/-/issues/1371. FTR the latest one is https://gitlab.com/api/v4/projects/4207231/packages/generic/graphviz-releases/2.49.3/graphviz-2.49.3.tar.xz and we expect them to be like this for the foreseeable future, https://gitlab.com/api/v4/projects/4207231/packages/generic/graphviz-releases/<version>/graphviz-<version>.tar.xz. However, we’re sort of at the mercy of Gitlab here. Please let me know if there’s anything further we (the upstream maintainers) can do to ease Debian packaging work.
