The other thing is that leaving regressions sitting in the tree with the notion
that somebody will fix it at some point is just not okay at all: that s***
*will* accumulate and cause hell to pay when the time to make the next release
comes. *Ideally* rpm should be release ready at any given commit.
As a general rule, if a regression can't be fixed on the spot, it's usually
better to revert and rethink.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1286#issuecomment-650064212
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
