Hello,

The Python team ends up filing a lot of keywordreqs due to new
dependencies.  Many of them end up open for many months, and start
listing obsolete package versions.  Then an arch team wakes up...
and adds keywords to a version that's supposed to be removed already. 
Or complains that the package list is outdated.

I think it's generally a reasonable assumption that keywordreq should be
applied to the newest version of a package, unless the keywordreq
explicitly says otherwise (in the comment).  It's not helpful that
stable-bot requires us to fill specific versions here.

I don't think it's fair to expect package maintainers to keep package
versions up-to-date in this case.  I can take the blame if the package
list becomes outdated, say, in 1 months.  If the arch team can't keyword
something in 6 months, I blame them, and I believe it should be their
responsibility to update the keywordreq.

Otherwise, we're creating a silly workflow where I keep putting
an effort into keeping the keywordreq up-to-date, hoping that one day
arch teams might actually act upon it.

How can we improve this?

-- 
Best regards,
Michał Górny