Project mappings for specific version ranges

[QuLogic]

In Fedora, Go packages are namespaced by their major version. With Go modules, the major version is part of the import path (i.e., the package "name" in Go), but would be sourced from the same repository. It's common to sometimes have 2 or 3 major versions still supported.

For example, gokrb5 is packaged in Fedora as golang-gopkg-jcmturner-gokrb5-5, the trailing 5 meaning it's for v5.y.z. However, when Anitya looks at tags, it sees v8.1.1 and sends a notification about that version.

It is currently set to Semantic, and I know that means I will never see any v5.y.z notifications. I guess setting it to Calendar would fix that, but then I'd still get notifications for v6, v7, v8, ..., which are meaningless for this package.

It would be nice to limit the range of notifications somehow, either as a property of the mapping, or as a constraint on the package (though that means multiple "packages" tracking each version.)

[Zlopez]

For now, you can try to solve this using custom backend and edit the regexp to only retrieve versions starting with 5. But this is not guarantee to work.