"version-diff" indeed is perhaps closer to what it does, however it just
happens that these tests depend on the version. There might as well be other
tests (in the future) that depend on some other baked-in value.
"release-prep" is similarly too generic because this really is just about the
tests, not necessarily about an imminent release (e.g. we need to "pin" these
tests even if we bump the micro version to .99 on master). But yup, I was too
thinking of having a "release" target that would automate some of the release
prep work, in which case this target would be made a dependency of it.
Other ideas:
* rebase-tests
* reproducible-tests (as this is the topic of the signature-verification test)
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2803#issuecomment-1849694517
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/2803/c1849694...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
