Optimistic testing of language targets

[Former user]

Keeping PYTHON_TARGETS and RUBY_TARGETS in pace with upstream development is a slow and boring manual process.

As a developer, I'd like to know when all package contraints for new language targets are satisfied and tests run successfully, so those targets can be updated in the tree.

If tests are available and run without any issues, this could end up in a semi-automatic process by filing a bug.

[Doug Freed]

I don't see how this is anything I need to worry about. You'd need the feature described in issue #6, but then you'd just submit a build job based on a branch with the updated ebuilds for the new version.