I went to ask the maintainer if it was okay to stabilize, but then realized that I did the 1.5.14 bump because he wasn't maintaining it...
(In reply to Matt Turner from comment #0) > I went to ask the maintainer if it was okay to stabilize, but then realized > that I did the 1.5.14 bump because he wasn't maintaining it... I am the maintainer for systemd-cron - you really should ask first per QA policy. Additionally, please refrain from purveying misinformation and Being judgmental, mean-spirited or insulting per the code of conduct. You, like any other dev, are welcome to co-maintain this or any other package in the repository if you wish.
Sorry dude. You haven't committed to the package in more than two years. If you can't be bothered to notice that your package doesn't have a stable version with Python 3.7 support and open the bug yourself, but you're concerned about *that* QA policy here I think you're focused on the wrong thing. I'll be happy to drop your name from metadata.xml so that it reflects reality.
Oh, hahaha. And the last commit you made was a stabilization requested by someone else. So the last time you touched the package as a maintainer was closer to three years ago.
amd64/sparc/x86 stable
