Support excluding certain github tag patterns

[omajid]

Some projects on github do releases for betas other non-final releases. It would be great if it was possible to exclude those versions from creating announcements/filing bugs.

One example is mockito. It currently includes many beta releases:

• v2.0.49-beta
• v2.0.48-beta
• ...

anitya shouldn't be announcing these releases (unless, maybe, if the developers ask for it).

[pypingou]

Well, it's a new version, it seems fair to me to announce it, down the road the package may chose to update or not rawhide with it, but upstream thought it was important enough to make a (pre)release with it, so I'm kinda inclined to keep it there.

[omajid]

I see what you are saying, but in this case, upstream has been doing betas every couple of weeks for a year or so. They haven't done a single non-beta release of "2.0". This may be part of some "release early, release often" development style. It's not suitable for inclusion in rawhide, I think because, as the documentation states, "keep in mind when the next Fedora release will be branched off, and be fairly confident that there will be a stable enough release in time for the next Fedora release." And we have no idea when the "2.0" version goes from beta to final.

Anyway, I am not suggesting changing defaults, but adding some way to let developers opt out of some notifications for some packages. I would be happy to work on a patch if you think this feature sounds sensible.

[pypingou]

If you're willing to work on it, I will be reviewing it :)